You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/02/02 22:54:36 UTC

[GitHub] [pulsar-helm-chart] frankjkelly opened a new pull request #224: Allow us to turn on PodSecurityPolicy for Pulsar clusters with the sa…

frankjkelly opened a new pull request #224:
URL: https://github.com/apache/pulsar-helm-chart/pull/224


   …me name deployed in different K8S namespaces in the same cluster. (PodSecurityPolicy is a cluster-level-resource so we are creating new PSPs by appending the pulsar namespace)
   
   Fixes #<xyz>
   
   ### Motivation
   
   * We want to be able to deploy multiple Pulsar clusters in different K8S namespaces but having the same helm release name. 
   
   ### Modifications
   
   * PodSecurityPolicies are cluster-wide so to avoid clashing we need to distinguish each Pulsar Cluster PSP somehow so we appended the `pulsar.namespace` value
   * For backwards compatiblity we keyed off of `rbac.limit_to_namespace` which by default is `false`
   https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/values.yaml#L93
   ### Verifying this change
   
   - [ ] Make sure that the change passes the CI checks.
   


-- 
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-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar-helm-chart] lhotari merged pull request #224: Allow us to turn on PodSecurityPolicy for Pulsar clusters with the same name deployed in different K8S namespaces in the same cluster

Posted by GitBox <gi...@apache.org>.
lhotari merged pull request #224:
URL: https://github.com/apache/pulsar-helm-chart/pull/224


   


-- 
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-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar-helm-chart] frankjkelly commented on pull request #224: Allow us to turn on PodSecurityPolicy for Pulsar clusters with the same name deployed in different K8S namespaces in the same cluster

Posted by GitBox <gi...@apache.org>.
frankjkelly commented on pull request #224:
URL: https://github.com/apache/pulsar-helm-chart/pull/224#issuecomment-1029360884


   @ckdarby good point `1.25` will be coming at some point later this year `1.24` looks due in April https://github.com/kubernetes/sig-release/tree/master/releases/release-1.24
   and with a release cycle every 15 weeks give or take that puts us I think in July/August timeframe if my math is correct.
   https://kubernetes.io/blog/2021/07/20/new-kubernetes-release-cadence/


-- 
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-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar-helm-chart] ckdarby commented on pull request #224: Allow us to turn on PodSecurityPolicy for Pulsar clusters with the same name deployed in different K8S namespaces in the same cluster

Posted by GitBox <gi...@apache.org>.
ckdarby commented on pull request #224:
URL: https://github.com/apache/pulsar-helm-chart/pull/224#issuecomment-1029349997


   Just an FYI, from [the docs](https://kubernetes.io/docs/concepts/policy/pod-security-policy/):
   > PodSecurityPolicy is deprecated as of Kubernetes v1.21, and will be removed in v1.25.


-- 
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-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org