-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Milestone
Description
Bug Report
What is the issue?
The communication between prometheus and the proxy should be using HTTPS but that is not the case.
How can it be reproduced?
Upgrade from version stable-2.9.1 to version edge-21.1.4
Initially, it was installed using:
linkerd install \
--identity-trust-anchors-file ca.crt \
--identity-issuer-certificate-file issuer.crt \
--identity-issuer-key-file issuer.key \
| kubectl apply -f -
For upgrading I did:
linkerdEdge upgrade | tee linkerd/base/linkerd.yaml
linkerdEdge viz install | tee linkerd/base/linkerd-viz.yaml
and argo replaced the old YAML files with the new ones.
Logs, error output, etc
INFO ThreadId(02) daemon:admin{listen.addr=0.0.0.0:4191}:accept{peer.addr=<prometheus pod ip>:35390 target.addr=<pgbouncer pod ip>:4191}: linkerd_app_core::serve: Connection closed error=proxy admin server is HTTP-only
linkerd check output
I have already rolled it back.
Environment
- Kubernetes Version: 1.16
- Kustomize Version: v3.8.1 (argo CD)
- Cluster Environment: (AWS)
- Linkerd version: edge-21.1.4
Possible solution
Maybe the same flags (for identity) should be available for viz
Additional context
I was using opaque-ports for pgbouncer (5432) and I have rolled it back already
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels