After uninstalling cert-manager, ingress resources can still only be accessed via https

[pptfz]

cert-manager version:v1.17.2

install ns:devops

Install using the following command

helm install \
  cert-manager jetstack/cert-manager \
  --namespace cert-manager \
  --create-namespace \
  --version v1.17.2 \
  --set crds.enabled=true

The current problem

In another ns, the access to ingress resources has all been changed to https. If http is accessed, only the nginx test page can be accessed. Why is that

For example, in the monitor command space, all ingress can only be accessed via https. Accessing http is the nginx test page

k -n monitor get ingress
NAME                      CLASS    HOSTS                      ADDRESS     PORTS     AGE
alertmanager              nginx    alertmanager.ops.com       localhost   80        19d
grafana                   <none>   grafana.ops.com            localhost   80        20d

k -n monitor get ingress grafana -o yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    meta.helm.sh/release-name: grafana
    meta.helm.sh/release-namespace: monitor
  creationTimestamp: "2025-04-08T10:47:02Z"
  generation: 1
  labels:
    app.kubernetes.io/instance: grafana
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: grafana
    app.kubernetes.io/version: 11.6.0
    helm.sh/chart: grafana-8.11.3
  name: grafana
  namespace: monitor
  resourceVersion: "638483"
  uid: 24667a78-a9da-4ee8-a5b2-366f0b33245f
spec:
  rules:
  - host: grafana.ops.com
    http:
      paths:
      - backend:
          service:
            name: grafana
            port:
              number: 80
        path: /
        pathType: Prefix
status:
  loadBalancer:
    ingress:
    - hostname: localhost

Accessing http is the nginx test page

Only by accessing https is it possible

It won't work even if I delete cert-manager

How should I solve this problem? Is it to restore grafana access through ingress 80 under the original monitor namespace

[fadecore]

Easy answer: Your topic has most likely nothing todo with cert-manager.

As long as you don't add relevant ingress annotations or define the tls part together with an extra certificate ressource you are simply not using cert-manager. Example from docs: https://cert-manager.io/docs/usage/ingress/

I couldn't get the problem correctly, but it looks like wrong ingress definitions in the first place.
If you open grafana via https in your browser - look at the certificate that is presented to you -> it is some ingress controller fake certificate, nothing that is provided by cert-manager.

[cert-manager-bot]

Issues go stale after 6 months of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues remain open for an additional 3 months of inactivity and then close.
If this issue is safe to close now please do so with /close.
/lifecycle stale

[cert-manager-bot]

Stale issues rot after 3 months of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 3 months of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale

[cert-manager-bot]

Rotten issues close after 3 months of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close

[cert-manager-prow]

@cert-manager-bot: Closing this issue.

Details

In response to this:

Rotten issues close after 3 months of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.