You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While connecting to vault using ArgoCD Vault Plugin getting login denied at F5 APM level
I was trying to connect vault cluster using argocd vault plugin for rendering secrets while deployment which are stored in hashicorp vault, i am getting blocked at F5 APM.
Error message and detailed steps followed for implementation are being noted down below, I would request please address this if someone has come across similar kind of issue.
Error
Unable to create application: application spec for testdemoapp is invalid: InvalidSpecError: Unable to generate manifests in .: rpc error: code = Unknown desc = plugin sidecar failed. error generating manifests in cmp: rpc error: code = Unknown desc = error generating manifests: argocd-vault-plugin generate ./ failed exit status 1: Error: Error making API request. URL: PUT https://kubernetes.default.svc.cluster.local/v1/auth/kubernates/login Code: 403. Raw Message: Forbidden by f5 APM (login denied) session reference: 25cb39ba31e3c58d631aa21e28ed7f44 Usage: argocd-vault-plugin generate [flags] Flags: -c, --config-path string path to a file containing Vault configuration (YAML, JSON, envfile) to use -h, --help help for generate -s, --secret-name string name of a Kubernetes Secret in the argocd namespace containing Vault configuration data in the argocd namespace of your ArgoCD host (Only available when used in ArgoCD). The namespace can be overridden by using the format : --verbose-sensitive-output enable verbose mode for detailed info to help with debugging. Includes sensitive data (credentials), logged to stderr
Have followed below steps for implementation: Environment Variables: have configured below env variables of vault as OpenShift secrets and referred them while deploying argocd instance as documented below.
Have created and build argocd custom image with vault plugin and used argocd operator for deploying argocd instance with plugin enabled as sidescar container along with argocd-repo-server shown below
Dockerfile:
FROM argoproj/argocd:v2.6.15
USER root
RUN apt-get clean -y
RUN rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*
COPY ca.crt client.crt client.key /vault/tls/client/
COPY argocd-vault-plugin_1.17.0_linux_amd64 argocd-vault-plugin
RUN chmod +x argocd-vault-plugin
RUN mv argocd-vault-plugin /usr/local/bin
USER 999
The text was updated successfully, but these errors were encountered:
azeem225
changed the title
login denied while connecting vault while using ArgoCD Vault Plugin
login denied while connecting vault using ArgoCD Vault Plugin
Apr 8, 2024
While connecting to vault using ArgoCD Vault Plugin getting login denied at F5 APM level
I was trying to connect vault cluster using argocd vault plugin for rendering secrets while deployment which are stored in hashicorp vault, i am getting blocked at F5 APM.
Have followed this below official documentation for configure and setup ArgoCD Vault Plugin.
https://argocd-vault-plugin.readthedocs.io/en/stable/
Error message and detailed steps followed for implementation are being noted down below, I would request please address this if someone has come across similar kind of issue.
Error
Unable to create application: application spec for testdemoapp is invalid: InvalidSpecError: Unable to generate manifests in .: rpc error: code = Unknown desc = plugin sidecar failed. error generating manifests in cmp: rpc error: code = Unknown desc = error generating manifests:
argocd-vault-plugin generate ./
failed exit status 1: Error: Error making API request. URL: PUT https://kubernetes.default.svc.cluster.local/v1/auth/kubernates/login Code: 403. Raw Message: Forbidden by f5 APM (login denied)session reference: 25cb39ba31e3c58d631aa21e28ed7f44 Usage: argocd-vault-plugin generate [flags] Flags: -c, --config-path string path to a file containing Vault configuration (YAML, JSON, envfile) to use -h, --help help for generate -s, --secret-name string name of a Kubernetes Secret in the argocd namespace containing Vault configuration data in the argocd namespace of your ArgoCD host (Only available when used in ArgoCD). The namespace can be overridden by using the format : --verbose-sensitive-output enable verbose mode for detailed info to help with debugging. Includes sensitive data (credentials), logged to stderr
Have followed below steps for implementation:
Environment Variables: have configured below env variables of vault as OpenShift secrets and referred them while deploying argocd instance as documented below.
Have created and build argocd custom image with vault plugin and used argocd operator for deploying argocd instance with plugin enabled as sidescar container along with argocd-repo-server shown below
Dockerfile:
Operator deployment file
Configmap:
Configmap for generating plugin.
The text was updated successfully, but these errors were encountered: