[GitHub] [pulsar-helm-chart] acjohnson commented on pull request #149: added extraVolumes and extraVolumeMounts

acjohnson commented on pull request #149: URL: https://github.com/apache/pulsar-helm-chart/pull/149#issuecomment-903045518 > @acjohnson please address the conflicts Rebased, conflicts resolved and still working -- This is an automated message from the Apache Git Service. To respond

[GitHub] [pulsar-helm-chart] acjohnson commented on pull request #149: added extraVolumes and extraVolumeMounts

acjohnson commented on pull request #149: URL: https://github.com/apache/pulsar-helm-chart/pull/149#issuecomment-903045456 > This change looks good to me at first glance. @acjohnson, have you done any testing yourself to see that this change renders properly? Yes it renders fine usin

[GitHub] [pulsar-helm-chart] acjohnson commented on pull request #150: added additionalCommand parameter

acjohnson commented on pull request #150: URL: https://github.com/apache/pulsar-helm-chart/pull/150#issuecomment-903044844 > Thank you for your contribution, @acjohnson. I am not opposed to adding a value like this, but I should point out that we are going to modify the pulsar docker image

[GitHub] [pulsar-helm-chart] acjohnson commented on a change in pull request #150: added additionalCommand parameter

acjohnson commented on a change in pull request #150: URL: https://github.com/apache/pulsar-helm-chart/pull/150#discussion_r693293606 ## File path: charts/pulsar/templates/bookkeeper-statefulset.yaml ## @@ -162,6 +162,9 @@ spec: command: ["sh", "-c"] args:

[GitHub] [pulsar-helm-chart] sijie commented on pull request #149: added extraVolumes and extraVolumeMounts

sijie commented on pull request #149: URL: https://github.com/apache/pulsar-helm-chart/pull/149#issuecomment-903020133 @acjohnson please address the conflicts -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL ab

[GitHub] [pulsar-helm-chart] sijie closed issue #125: Append Configuration of ImagePullSecret

sijie closed issue #125: URL: https://github.com/apache/pulsar-helm-chart/issues/125 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr.

[GitHub] [pulsar-helm-chart] sijie merged pull request #140: Add Support for imagePullSecrets

sijie merged pull request #140: URL: https://github.com/apache/pulsar-helm-chart/pull/140 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsu

Re: [PROPOSAL] Defining a clearer process for PIP proposals

> Thanks for working on this. I've been wondering about this for a while now. > > Is the expectation that a PR with proposed changes must already be created > before a PIP is added to the Wiki? I've felt a little confused about this > in the past when trying to start discussions or get feedback on

Re: [PROPOSAL] Defining a clearer process for PIP proposals

Matteo, Thanks for working on this. I've been wondering about this for a while now. Is the expectation that a PR with proposed changes must already be created before a PIP is added to the Wiki? I've felt a little confused about this in the past when trying to start discussions or get feedback on

[GitHub] [pulsar-helm-chart] michaeljmarshall commented on a change in pull request #150: added additionalCommand parameter

michaeljmarshall commented on a change in pull request #150: URL: https://github.com/apache/pulsar-helm-chart/pull/150#discussion_r693247604 ## File path: charts/pulsar/templates/bookkeeper-statefulset.yaml ## @@ -162,6 +162,9 @@ spec: command: ["sh", "-c"] ar

Re: Proposing a meetup organizing committee

The conversation here seems incoherent because of a few factors. One is by the use of "community'' and "project" interchangeably, as required to support this proposal - community in one context to support holding meetups/conferences and at the same time asking the PMC to manage this effort un

Re: Proposing a meetup organizing committee

BCC: private@ The bulk of this discussion should proceed with good intent on dev@ with a separate thread on private@ only if needed. I have prepared a set of links to documentation about the Apache Way that is worth reviewing: https://petri.apache.org/way Hierar

Re: Proposing a meetup organizing committee

*I think the Apache project should avoid vendor-specific branding, in that way users will have a clear understanding about what they can receive from the free Apache project. In support of that, the Apache project should be driven by the community/PMC who are the real contributors to the project an