Comments (10)
When I auth to argocd with username/password, I don't get NOAUTH errors. When I auth to argocd with --core
, I do get NOAUTH errors.
Something about the new redis auth is tied to argocd auth, which, when bypassed, causes redis to also not authenticate.
from argo-cd.
What was your kube context at the moment you added the cluster? See
I was using the rdr-hub context and in the argocd namespace, that is why I still could run login --core
and add another cluster.
Thanks for the slack info, I could also ask in the slack channel.
from argo-cd.
NOAUTH Authentication required
seems to be a redis error. There was changes in the latest version of argocd to add basic authentication. A password should have been generated automatically in the argocd-redis
secret by the argocd-redis-ha
deployment init container. You can check if REDIS_PASSWORD is defined in your argocd-server
deployment as a variable. Make sure you use at least version 7.1.1 of https://github.com/argoproj/argo-helm/tree/main/charts/argo-cd, or deployment manifests that will configure redis authentication.
from argo-cd.
What was your kube context at the moment you added the cluster? See
argo-cd/cmd/argocd/commands/cluster.go
Lines 53 to 54 in 2639c59
You might want to join the CNCF slack to ask usage questions in https://cloud-native.slack.com/archives/C01TSERG0KZ instead of bug reports. https://github.com/argoproj/argo-cd/discussions is also a good place if you don't have access to Slack.
from argo-cd.
In the argocd-server pod definition, I see it has following:
containers:
- args:
- /usr/local/bin/argocd-server
env:
- name: REDIS_PASSWORD
valueFrom:
secretKeyRef:
key: auth
name: argocd-redis
Secret argocd-redis exists in the argocd namespace, contains data/auth key and value.
Argocd cluster add command should atuo read this secret to access redis server, right?
from argo-cd.
btw, argocd is deployed using:
kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
I followed document of https://argo-cd.readthedocs.io/en/stable/getting_started/
from argo-cd.
In the steps above, you login to Argo CD in core mode, but it seems like you installed the full manifest. I think if you remove the --core, it should work normally. But you might have found a problem with the CLI usage in core mode.
$ argocd login --core
Context 'kubernetes' updated
from argo-cd.
btw, argocd is deployed using: kubectl create namespace argocd kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
I followed document of https://argo-cd.readthedocs.io/en/stable/getting_started/
@agaudreault is correct. If you installed all vended manifests (install.yaml), there is no reason for you to run the Argo CD CLI in core mode (--core
). That is only required if you are just deploying the Argo CD controller without the API server.
from argo-cd.
Today I created two new minikube clusters, and installed argocd core in the rdr-hub cluster, by using file of https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/core-install.yaml
I checked, this time in the argocd ns, I only have below pods:
$ kubectl get pod
NAME READY STATUS RESTARTS AGE
argocd-application-controller-0 1/1 Running 0 19m
argocd-applicationset-controller-7dc76d94b4-8thzw 1/1 Running 0 19m
argocd-redis-545f8544bb-5sxrf 1/1 Running 0 19m
argocd-repo-server-7c55f55c7-7vwk7 1/1 Running 0 19m
After login --core and add the other cluster in, it reports the same issue.
$ argocd login --core
Context 'kubernetes' updated
$ argocd cluster add rdr-dr1
WARNING: This will create a service account `argocd-manager` on the cluster referenced by context `rdr-dr1` with full cluster level privileges. Do you want to continue [y/N]? y
INFO[0003] ServiceAccount "argocd-manager" created in namespace "kube-system"
INFO[0003] ClusterRole "argocd-manager-role" created
INFO[0003] ClusterRoleBinding "argocd-manager-role-binding" created
INFO[0008] Created bearer token secret for ServiceAccount "argocd-manager"
ERRO[0009] finished unary call with code Unknown error="NOAUTH Authentication required." grpc.code=Unknown grpc.method=Create grpc.service=cluster.ClusterService grpc.start_time="2024-06-06T12:20:35+05:30" grpc.time_ms=206.557 span.kind=server system=grpc
FATA[0009] rpc error: code = Unknown desc = NOAUTH Authentication required.
$ argocd cluster list
SERVER NAME VERSION STATUS MESSAGE PROJECT
https://192.168.22.71:8443 rdr-dr1
https://kubernetes.default.svc in-cluster
So this does look like a bug, even I only installed with core mode.
from argo-cd.
relates to #19035, and should be fixed by #19599.
When using --core
flag, a local argocd server is being created without the Redis password, thus resulting in NOAUTH
error
from argo-cd.
Related Issues (20)
- Enable ignoreResourceUpdate by default with known high churn resources
- Allow forks to opt-in for codeql HOT 1
- Inconsistent StatefulSet patching when container names change after disabling ServerSideApply and ServerSideDiff
- ? HOT 1
- Fetching Argo CD repository resource returns "Permission Denied" instead of "Not Found". HOT 3
- Request for Fixing Identified Vulnerabilities in ArgoCD 2.11.8
- Automatic cleanup for stale issues HOT 7
- Show pod names state should be applied when logs popped out HOT 3
- Ignore known Kubernetes internal resources by default with `resource.exclusions`
- The `--core` flag is being ignored when using `ARGOCD_OPTS` env variable HOT 1
- rpc error: code = Unknown desc = NOAUTH Authentication required
- Critical CVE in docker library dependency in v2.12.3
- AppSet with create-update syncPolicy reports as Synced when there are Apps to be deleted
- Bump issue #15184 - deprecate argocd-notifications docs site HOT 1
- Bump issue #15184 - deprecate argocd-notifications docs site HOT 1
- Ellipsis menu for pod logs opens a loading thing and then disappears HOT 2
- Race: repository.TestGenerateManifestsHelmWithRefs_CachedNoLsRemote
- Terminal into Pod is not possible if authentication was disabled HOT 1
- api/webhook not triggering refresh of Azure DevOps Repos HOT 14
- Adding a Health Check Endpoint to ArgoCD Notification HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from argo-cd.