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.

Sign up for GitHub

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

Jump to bottom

Seldon Core Operator defaulting causes issues with helm and ArgoCD #233

Closed
ukclivecox opened this issue Sep 24, 2018 · 0 comments · Fixed by #238
Closed

Seldon Core Operator defaulting causes issues with helm and ArgoCD #233

ukclivecox opened this issue Sep 24, 2018 · 0 comments · Fixed by #238
Assignees
@ukclivecox

Comments

@ukclivecox
Copy link
Contributor

The Operator has a defaulting initial step which updates missing settings with defaults. These are pushed back to the K8S API to update the custom resource. However, this may cause issues with Helm and ArgoCD as they see changes from the raw original custom resources. Investigation is needed to see how k8s expects custom resources to be handled with respect to defaulting.
Deployment mechanisms such as ksonnet which are more light touch on state don't have this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ukclivecox ukclivecox

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix for defaulting changing Custom Resource
1 participant
@ukclivecox