-
Notifications
You must be signed in to change notification settings - Fork 0
Feature/121.2 apply blueprint continuously #127
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
base: feature/121-apply-blueprint-continuously
Are you sure you want to change the base?
Feature/121.2 apply blueprint continuously #127
Conversation
…ntinuously' into feature/121.2-apply-blueprint-continuously
…ency [#125] ignore nginx dependency
…y-blueprint-continuously # Conflicts: # CHANGELOG.md # pkg/application/stateDiffUseCase_test.go # pkg/domain/dogu_test.go # pkg/domainservice/validateDependenciesDomainUseCase.go
The LastApplySucceeded contains any errors happening in the apply steps. It greatly reduces the complexity of setting conditions, because it will not reset at StateDiff in contrast to the Applied-Conditions before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a first quick look for now.
values: | ||
images: | ||
blueprintOperator: cloudogu/k8s-blueprint-operator:2.7.0 | ||
blueprintOperator: cloudogu/k8s-blueprint-operator:2.8.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are these changes from the original develop/main?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, is this bad? We needed them for the test with argoCD. Are we not allowed to merge it into V2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just looked at the changes again and they all seem compatible with v2
pkg/adapter/kubernetes/blueprintcr/v2/blueprintSpecCRRepository.go
Outdated
Show resolved
Hide resolved
pkg/adapter/kubernetes/blueprintcr/v2/blueprintSpecCRRepository.go
Outdated
Show resolved
Hide resolved
This is unnecessary, because it will be recalculated on every reconciliation
This is necessary to avoid potential restarts of dogus with unfitting config (for another dogu version)
No description provided.