-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Switch to kustomize2 as default. Add argocd-ha install manifests #1169
Conversation
12c206d
to
2632b93
Compare
Codecov Report
@@ Coverage Diff @@
## master #1169 +/- ##
=========================================
Coverage ? 35.98%
=========================================
Files ? 59
Lines ? 8563
Branches ? 0
=========================================
Hits ? 3081
Misses ? 5026
Partials ? 456
Continue to review full report at Codecov.
|
e4097fc
to
69431a1
Compare
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 can't comment on many of the HA changes I'm afraid. The Kustomize 2 work LGTM.
@@ -44,7 +44,8 @@ spec: | |||
repo: "{{workflow.parameters.repo}}" | |||
revision: "{{workflow.parameters.revision}}" | |||
container: | |||
image: argoproj/argo-cd-ci-builder:latest | |||
image: argoproj/argo-cd-ci-builder:v0.12.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.
???
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.
Ah yes. Because I am changing the meaning of kustomize
from 1 to 2, the unit tests will fail unless I publish a new "builder image". But since the same build image is used for other branches (e.g. release-0.11) it means if everyone is using :latest
, then I will break the release-0.11 branch builds. It was an eventuality that we would need to start versioning the builder images, this was the first time we needed to.
@@ -27,3 +20,9 @@ to return `Progressing` state instead of `Healthy`. | |||
include the fix [kubernetes/kubernetes#67570](https://github.com/kubernetes/kubernetes/pull/67570) `StatefulSet` might stay in `Progressing` state. | |||
|
|||
As workaround Argo CD allows providing [health check](health.md) customization which overrides default behavior. | |||
|
|||
## I forgot the admin password, how do I reset it? |
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.
No one ever does this 😂
docs/declarative-setup.md
Outdated
## Applications | ||
|
||
The Application CRD is the Kubernetes resource object representing a deployed application instance | ||
in an environment. It is defined by two key pieces of information: | ||
* `source` reference to the desired state in git (repository, revision, path, environment) | ||
* `destination` reference to the target cluster and namespace. | ||
|
||
An example Application spec is as follows: | ||
An minimal Application spec is as follows: |
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.
An minimal
-> A minimal
69431a1
to
1b10fac
Compare
1b10fac
to
eafbd95
Compare
kustomize
in the path refers to kustomize 2. likewise, assumes kustomize1 exists in path, which refers to kustomize 1