简体   繁体   English

kubernetes cert-manager 忽略入口注释

[英]kubernetes cert-manager ignores ingress annotations

I've set up Kubernetes with nginx ingress and cert-manager.我已经使用 nginx 入口和证书管理器设置了 Kubernetes。 I want to use ECDSA Certificate instead of RSA certificate so I followed the documentation and set cert-manager.io/private-key-algorithm: ECDSA in Ingress configuration.我想使用 ECDSA 证书而不是 RSA 证书,所以我遵循文档并在入口配置中设置cert-manager.io/private-key-algorithm: ECDSA Unfortunately cert-manager seems to ignore this setting and creating a RSA certificate.不幸的是 cert-manager 似乎忽略了这个设置并创建了一个 RSA 证书。

kind: Ingress
apiVersion: networking.k8s.io/v1
metadata:
  name: {{ include "myapp.fullname" . }}-ingress
  labels:
    {{- include "myapp.labels" . | nindent 4 }}
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
    cert-manager.io/issuer: {{ .Values.certManager.name }}
    cert-manager.io/private-key-algorithm: ECDSA
spec:
  ingressClassName: nginx
  tls:
    - hosts:
      - {{ .Values.ingressHostName }}
      secretName: "{{ include "myapp.fullname" . }}-{{ .Values.certManager.privateKeySecretRef }}"
  rules:
    - host: {{ .Values.ingressHostName }}
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: {{ .Values.landingpage.frontend.service.fullname }}
                port:
                  number: {{ .Values.landingpage.frontend.service.port }}
apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
  name: {{ .Values.certManager.name }}
spec:
  acme:
    # The ACME server URL
    server: {{ .Values.certManager.server }}
    # Email address used for ACME registration
    email: {{ .Values.certManager.email }}
    # Name of a secret used to store the ACME account private key
    privateKeySecretRef:
      name: "{{ include "myapp.fullname" . }}-cert-manager-key"
    # Enable the HTTP-01 challenge provider
    solvers:
    - http01:
        ingress:
          class:  nginx

It does not appear you can do this via the ingress resource yet, but you can do it via the Certificate resource:您似乎还不能通过入口资源执行此操作,但您可以通过证书资源执行此操作:

https://github.com/cert-manager/cert-manager/issues/2567 https://github.com/cert-manager/cert-manager/issues/2567

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 使用cert-manager istio ingress和LetsEncrypt在kubernetes中配置SSL证书 - Configure SSL certificates in kubernetes with cert-manager istio ingress and LetsEncrypt 带有证书管理器和自签名 ClusterIssuer 的 Kubernetes TLS Ingress 路由不起作用 - Kubernetes TLS Ingress route with cert-manager and SelfSigned ClusterIssuer not working Kubernetes 证书管理器 GoDaddy - Kubernetes cert-manager GoDaddy Kubernetes 证书管理器问题 - Kubernetes cert-manager issue 如何更新 istio 的 helm 安装以启用 'Kubernetes Ingress with Cert-Manager' 或 'enable SDS at ingress gateway' - how update the helm installation of istio to enable 'Kubernetes Ingress with Cert-Manager' or 'enable SDS at ingress gateway' 未应用带有证书管理器的入口TLS路由 - Ingress TLS routes with cert-manager not applied ingress-nginx、cert-manager 和 ingressClassName - ingress-nginx, cert-manager and ingressClassName Kong Ingress cert-manager 路由错误 - Kong Ingress cert-manager wrong routing AWS上的Kubernetes:使用Nginx-ingress + cert-manager保留客户端IP - Kubernetes on AWS: Preserving Client IP with nginx-ingress + cert-manager 通配符让我们使用 cert-manager、nginx 入口、kubernetes 中的 cloudflare 加密证书如何解决? - Wildcard Let's Encrypt certificates with cert-manager, nginx ingress, cloudflare in kubernetes how to fix?
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM