Describe the bug
I am using service resgistration on Vault config : service_registration "kubernetes" {} and on my manifest using Downward API:
- name: VAULT_K8S_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: VAULT_K8S_POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
To Reproduce
Steps to reproduce the behavior:
- Run
kubectl apply -f .
- Vault logs:
2020-11-05T12:13:22.494Z [WARN] service_registration.kubernetes: unable to set initial state due to bad status code: req method: GET, req url: https://x.x.x.x:443/api/v1/namespaces/vault/pods/vault-deployment-5bcf69d947-jd9jj, resp statuscode: 403, will retry
Expected behavior
Get this information :
apiVersion: v1
kind: Pod
metadata:
name: vault
labels:
vault-active: "false"
vault-initialized: "true"
vault-perf-standby: "false"
vault-sealed: "false"
vault-version: 1.3.0
Environment:
- Vault Server Version (retrieve with
vault status):
Key Value
--- -----
Recovery Seal Type shamir
Initialized true
Sealed false
Total Recovery Shares 1
Threshold 1
Version 1.5.5
Cluster Name vault-cluster-c9b1f457
Cluster ID c33a4edb-20ec-d9d7-c94d-376bfc42e8fb
HA Enabled true
HA Cluster https://x.x.x.x:8201
HA Mode active
- Vault CLI Version (retrieve with
vault version): Vault v1.5.5
- Server Operating System/Architecture:
Kubernetes
Describe the bug
I am using service resgistration on Vault config :
service_registration "kubernetes" {}and on my manifest using Downward API:To Reproduce
Steps to reproduce the behavior:
kubectl apply -f .2020-11-05T12:13:22.494Z [WARN] service_registration.kubernetes: unable to set initial state due to bad status code: req method: GET, req url: https://x.x.x.x:443/api/v1/namespaces/vault/pods/vault-deployment-5bcf69d947-jd9jj, resp statuscode: 403, will retry
Expected behavior
Get this information :
Environment:
vault status):vault version):Vault v1.5.5Kubernetes