Skip to content

Bump proxy-init:v2.2.3 and cni-plugin:v1.2.2#11399

Merged
alpeb merged 1 commit intomainfrom
alpeb/proxy-init_cni-plugin_bumps
Sep 21, 2023
Merged

Bump proxy-init:v2.2.3 and cni-plugin:v1.2.2#11399
alpeb merged 1 commit intomainfrom
alpeb/proxy-init_cni-plugin_bumps

Conversation

@alpeb alpeb requested a review from a team as a code owner September 20, 2023 13:36
| profileValidator.injectCaFromSecret | string | `""` | Inject the CA bundle from a Secret. If set, the `cert-manager.io/inject-ca-from-secret` annotation will be added to the webhook. The Secret must have the CA Bundle stored in the `ca.crt` key and have the `cert-manager.io/allow-direct-injection` annotation set to `true`. See the cert-manager [CA Injector Docs](https://cert-manager.io/docs/concepts/ca-injector/#injecting-ca-data-from-a-secret-resource) for more information. |
| profileValidator.keyPEM | string | `""` | Certificate key for the service profile validator. If not provided and not using an external secret then Helm will generate one. |
| profileValidator.namespaceSelector | object | `{"matchExpressions":[{"key":"config.linkerd.io/admission-webhooks","operator":"NotIn","values":["disabled"]}]}` | Namespace selector used by admission webhook |
| prometheusUrl | string | `""` | url of external prometheus instance (used for the heartbeat) |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems unrelated to proxyInit?

Copy link
Member

@mateiidavid mateiidavid Sep 21, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's from a previous change where bin/helm-docs wasn't run. Seems to be unavoidable when generating the docs. For the backport it might be okay, if the field isn't present in values.yaml it will get removed once we bump the charts and re-generate the docs.

@alpeb does that sound right to you?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand why the doc diff wasn't caught by CI in earlier runs, but it looks like this PR puts it back in track.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants