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

Switch to kustomize2 as default. Add argocd-ha install manifests #1169

Merged
merged 1 commit into from
Feb 25, 2019

Conversation

jessesuen
Copy link
Member

@jessesuen jessesuen commented Feb 23, 2019

  1. updates manifests to use kustomize 2
  2. switches assumption that kustomize in the path refers to kustomize 2. likewise, assumes kustomize1 exists in path, which refers to kustomize 1
  3. adds HA versions of installation manifests
  4. adds a script to easily pull redis-ha from upstream chart, and apply local kustomizations
  5. update dex to v2.14.0
  6. improve documentation

@jessesuen jessesuen requested review from alexmt and alexec February 23, 2019 13:26
@jessesuen jessesuen force-pushed the kustomize2 branch 2 times, most recently from 12c206d to 2632b93 Compare February 24, 2019 01:17
@codecov-io
Copy link

codecov-io commented Feb 24, 2019

Codecov Report

❗ No coverage uploaded for pull request base (master@e0594aa). Click here to learn what that means.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff            @@
##             master    #1169   +/-   ##
=========================================
  Coverage          ?   35.98%           
=========================================
  Files             ?       59           
  Lines             ?     8563           
  Branches          ?        0           
=========================================
  Hits              ?     3081           
  Misses            ?     5026           
  Partials          ?      456
Impacted Files Coverage Δ
util/kustomize/kustomize.go 77.45% <100%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e0594aa...eafbd95. Read the comment docs.

@jessesuen jessesuen force-pushed the kustomize2 branch 3 times, most recently from e4097fc to 69431a1 Compare February 25, 2019 10:13
Copy link
Contributor

@alexec alexec left a 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
Copy link
Contributor

Choose a reason for hiding this comment

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

???

Copy link
Member Author

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?
Copy link
Contributor

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 😂

## 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:
Copy link
Collaborator

Choose a reason for hiding this comment

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

An minimal -> A minimal

@jessesuen jessesuen merged commit 3395395 into argoproj:master Feb 25, 2019
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.

4 participants