Skip to content

[new-product] Add Argo CD#3337

Merged
captn3m0 merged 12 commits intoendoflife-date:masterfrom
adriens:patch-19
Aug 5, 2023
Merged

[new-product] Add Argo CD#3337
captn3m0 merged 12 commits intoendoflife-date:masterfrom
adriens:patch-19

Conversation

@adriens
Copy link
Copy Markdown
Contributor

@adriens adriens commented Jul 30, 2023

❔ About

Argo CD is a very widely used solution around K8S, GitOPS : it makes it possible to deploy in a very comfortable way.

Declarative continuous deployment for Kubernetes.

It gains everyday in traction, so it deserves its page on endoflife.date 🦑

argocd-ui

🦑  Argo CD is a very widely used solution for CD within K8S GitOPS.
Copy link
Copy Markdown
Member

@captn3m0 captn3m0 left a comment

Choose a reason for hiding this comment

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

Not sure about the EOL dates. The policy is also differing in both the pages, so its unclear if eol(x) = releaseDate(x+2) or eol(x) = releaseDate(x+3).

I've raised it in the argo-cd chat, lets wait to get a reply before finalizing.

@adriens
Copy link
Copy Markdown
Contributor Author

adriens commented Jul 31, 2023

@captn3m0

I've raised it in the argo-cd chat, lets wait to get a reply before finalizing.

great idea 🤩 Hopefully we will appreciate the effort 🤞

adriens and others added 2 commits August 1, 2023 07:59
Co-authored-by: Nemo <commits@captnemo.in>
@marcwrobel marcwrobel changed the title [new-product] Add "Argo CD" [new-product] Add Argo CD Jul 31, 2023
@marcwrobel marcwrobel added the new-product This PR adds a new product to the website. label Jul 31, 2023
adriens and others added 7 commits August 1, 2023 08:05
Co-authored-by: Nemo <commits@captnemo.in>
Co-authored-by: Nemo <commits@captnemo.in>
Co-authored-by: Nemo <commits@captnemo.in>
Co-authored-by: Nemo <commits@captnemo.in>
update eol considering eol strategy cf #3337 (comment)
Lets not include releases prior to 1.0. as per of : 
cf #3337 (comment)
Co-authored-by: Nemo <commits@captnemo.in>
@adriens
Copy link
Copy Markdown
Contributor Author

adriens commented Jul 31, 2023

For now I have applied the eol(x) = releaseDate(x+2) rule.

@captn3m0
Copy link
Copy Markdown
Member

captn3m0 commented Aug 1, 2023

The policy is now updated:

We currently support the last 3 minor versions of Argo CD with security and bug fixes.

PR: argoproj/argo-cd#14786

So eol(X) = releaseDate(X+3).

@adriens
Copy link
Copy Markdown
Contributor Author

adriens commented Aug 2, 2023

Ok, I'll apply the eol policy data based on +3 rule ⚡

Applying eol policy (+3)
@adriens
Copy link
Copy Markdown
Contributor Author

adriens commented Aug 2, 2023

new eols pushed 🚀

@adriens
Copy link
Copy Markdown
Contributor Author

adriens commented Aug 5, 2023

Hi @captn3m0 , does it look good enough to be merged ?... or is there some more stuff to be done ?

@adriens
Copy link
Copy Markdown
Contributor Author

adriens commented Aug 5, 2023

... or still waiting for

Copy link
Copy Markdown
Member

@captn3m0 captn3m0 left a comment

Choose a reason for hiding this comment

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

EOLs look good, I added some identifiers as well. Merging.

@captn3m0 captn3m0 merged commit 6e5d097 into endoflife-date:master Aug 5, 2023
@adriens
Copy link
Copy Markdown
Contributor Author

adriens commented Aug 5, 2023

EOLs look good, I added some identifiers as well.

Yes, that's great :

identifiers:
-   repology: argocd
-   purl: pkg:docker/argoproj/argocd
-   purl: pkg:oci/argocd?repository_url=quay.io/argoproj
-   purl: pkg:oci/argocd?repository_url=ghcr.io/argoproj
-   purl: pkg:github/argoproj/argo-cd

🤔 Should we also add the ones for :

@adriens adriens deleted the patch-19 branch August 5, 2023 21:56
@adriens
Copy link
Copy Markdown
Contributor Author

adriens commented Aug 5, 2023

Tweet

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-product This PR adds a new product to the website.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants