Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add toggle features for Kafka and minor fixes around operator plan #239

Merged
merged 2 commits into from
Mar 24, 2020

Conversation

zmalik
Copy link
Member

@zmalik zmalik commented Mar 19, 2020

this PR:

  • add Toggle task for all features present in KUDO Kafka
  • update the minimal KUDO version to 0.11.0 because of Toggle Task usage
  • add a section of planned releases in README.md for unreleased versions to avoid any confusion
  • separate deploy and update plans, to avoid running pipe task in each update. This should also reduce the test duration in all CI pipelines
  • modify the autoTLS feature so it only generates certs when enabled
  • migrate mirrormaker and user workload to use apps/v1
  • remove the usage of $root as Add verifier support for the special $ variable. kudo#1255 was merged and released

@zmalik zmalik self-assigned this Mar 19, 2020
Signed-off-by: Zain Malik <zmalikshxil@gmail.com>
- health-check.yaml
- enable-tls.yaml
- user-workload.yaml
# task used to restrict patching sts where it is not allowed
- name: not-allowed
kind: Dummy
Copy link
Member

Choose a reason for hiding this comment

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

On the topic of the not-allowed task: Would it make sense to have a task type "Fail" that simply FATAL_ERRORs the plan with a specified message?

Copy link
Member Author

Choose a reason for hiding this comment

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

yeah we need to do another round here now after many releases

Copy link
Member

Choose a reason for hiding this comment

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

Actually, I think we really need immutable parameters. Having the task is ok-ish for now, but the parameters still get set even if the plan fails. And on the next run of update they're applied

Copy link
Contributor

Choose a reason for hiding this comment

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

And our admission controller would be able to prevent changing immutable parameters. We need a KEP for that but otherwise, the solution can be pretty simple.

Copy link
Member

@ANeumann82 ANeumann82 left a comment

Choose a reason for hiding this comment

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

Looks good to me. I'm probably not grasping all the details, but I couldn't see any obvious issues

Signed-off-by: Zain Malik <zmalikshxil@gmail.com>
@zmalik zmalik requested a review from zen-dog March 23, 2020 09:29
Copy link
Contributor

@zen-dog zen-dog left a comment

Choose a reason for hiding this comment

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

Nice work! 🚢

@zmalik zmalik merged commit f32267b into master Mar 24, 2020
@zmalik zmalik deleted the zain/kafka-toggle branch March 24, 2020 11:55
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