-
Notifications
You must be signed in to change notification settings - Fork 4
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
local/staging: use argocd-config 1.0.5 (deploys api) #1782
Draft
deer-wmde
wants to merge
25
commits into
main
Choose a base branch
from
de/local-staging-argocd-config-1.0.3
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rosalieper
approved these changes
Sep 23, 2024
could you please update the PR description too? |
deer-wmde
changed the title
local/staging: use argocd-config 1.0.3 (deploys api)
local/staging: use argocd-config 1.0.5 (deploys api)
Sep 23, 2024
This seems to work, we just still run into https://phabricator.wikimedia.org/T375268 |
* remove api preinstall job workaround * remove temp files
n.b. this doesn't impact queryservice Bug: T375866
* Create multi-tenancy-vs-federation.md Add a very high level doc about the difference between multi-tenancy and federation * Update multi-tenancy-vs-federation.md
This commit adds a new node pool to replace the exiting one. It uses smaller machines to free up some capacity. The commit removing the existing node pool will happen later. Bug: T376117
This increases the memory since we suspect that's why it now fails to start. It was stuck in crashloop backoff exiting with code 139 See: argoproj/argo-cd#15786 Bug: T376117
Set cpu limits to 0 for most workloads for production Bug: T375874
* fix: creating local cluster fails on CPU limit * Update local ArgoCD config * fix: creating local cluster fails on Nginx webhook (#1803)
* reduce cert manager log level * add missing newline * remove blank line * fix value key * fix key
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://phabricator.wikimedia.org/T374217
Uses argocd-config chart v1.0.5 which adds the platform api to argocd deployments wbstack/charts#160
edit: changed to v1.0.5 due to two version bumps