Confusion around upgrading from v1beta2 to v1 #12197
Replies: 1 comment
-
|
That is indeed confusing. There will be some improvements around this in the 0.49.1 docs. You can see how the config would look like for example in the latest docs builds from the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I saw in the release notes that v1 versions of the CRDs had been rolled out now. In the release notes, it states that in the authentication and authorization fields
type: oauthandtype: keycloakrespectively has been replaced bytype: custom. My v1beta2 manifest currently looks like this:In the docs for manual changes that has to be made on the Kafka resource it says to replace oauth with custom and instead mount the secrets using the
templatesection. In the v1 CRD, the authentication section looks like this:It no longer contains properties like clientId, validIssuerUri, etc. either so I assume these should be moved somewhere else as well? In the oauth section of the documentation it still uses
type: oauthdespite using the v1 manifest as well which is kinda confusing. Any clarification on this? Is the documentation just not fully updated yet? Help much appreciated 😃Beta Was this translation helpful? Give feedback.
All reactions