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

Pin Helm versions to docs version #1249

Open
johnharris85 opened this issue Mar 1, 2023 · 10 comments
Open

Pin Helm versions to docs version #1249

johnharris85 opened this issue Mar 1, 2023 · 10 comments
Labels
good first issue Good for newcomers kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@johnharris85
Copy link
Contributor

Description

We should ensure that the helm installation instructions also specify the correct version of the chart that corresponds to the currently browsed version of the docs (like we do for kumactl install commands).
@johnharris85 johnharris85 added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature labels Mar 1, 2023
@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Mar 6, 2023
@slonka
Copy link
Contributor

slonka commented Mar 6, 2023

I found old kuma website deployment and the helm instructions did not have a version pinned - https://deploy-preview-1013--kuma.netlify.app/docs/1.6.x/installation/helm/#run-kuma. We did pinning in 1.4 - https://kuma.io/docs/1.4.x/installation/helm/. So I guess we just stopped after 1.4, nothing to do with the docs migration.

@github-actions
Copy link
Contributor

github-actions bot commented Jun 5, 2023

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jun 5, 2023
@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label Jun 12, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Sep 11, 2023
@github-actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@jakubdyszkiewicz jakubdyszkiewicz removed the triage/stale Inactive for some time. It will be triaged again label Sep 15, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Dec 15, 2023
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@jakubdyszkiewicz jakubdyszkiewicz added triage/pending This issue will be looked at on the next triage meeting triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/stale Inactive for some time. It will be triaged again triage/accepted The issue was reviewed and is complete enough to start working on it triage/pending This issue will be looked at on the next triage meeting labels Dec 18, 2023
@jakubdyszkiewicz
Copy link
Contributor

Triage: still relevant. For example here https://kuma.io/docs/2.5.x/production/cp-deployment/stand-alone/ we should add --version to pick proper helm chart version (that is equal to kuma version)

@jakubdyszkiewicz jakubdyszkiewicz added the good first issue Good for newcomers label Dec 18, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Mar 18, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@jakubdyszkiewicz jakubdyszkiewicz removed the triage/stale Inactive for some time. It will be triaged again label Mar 18, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jun 17, 2024
@lobkovilya lobkovilya removed the triage/stale Inactive for some time. It will be triaged again label Jun 17, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Sep 16, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@slonka
Copy link
Contributor

slonka commented Sep 16, 2024

we're still not doing that https://kuma.io/docs/2.8.x/production/cp-deployment/single-zone/

@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label Sep 16, 2024
@Automaat Automaat mentioned this issue Oct 30, 2024
Open
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Dec 16, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@johnharris85 @slonka @jakubdyszkiewicz @lobkovilya @lukidzi