NGINX configmap/ingress-nginx-controller reset on every startup

[logopk]

What Happened?

My SSL Hardening settings are reset on every startup of minikube to
hsts: "false" .

I have tried to add my personal addon to ~/.minikube/addons/ingress-deploy.yaml (16490 bytes).
the file is copied via ssh to the server, but upon deployment it is taken from "memory" (whatever that is) and reset to the tmpl-Version from the github repo https://github.com/kubernetes/minikube/blob/master/deploy/addons/ingress/ingress-deploy.yaml.tmpl

I0307 18:07:29.955380   94826 filesync.go:126] Scanning /Users/logo/.minikube/addons for local assets ...
I0307 18:07:29.955727   94826 filesync.go:149] local asset: /Users/logo/.minikube/addons/ingress-deploy.yaml -> ingress-deploy.yaml in /etc/kubernetes/addons
I0307 18:07:29.955770   94826 vm_assets.go:163] NewFileAsset: /Users/logo/.minikube/addons/ingress-deploy.yaml -> /etc/kubernetes/addons/ingress-deploy.yaml
I0307 18:07:29.960826   94826 ssh_runner.go:195] Run: stat -c "%!s(MISSING) %!y(MISSING)" /etc/kubernetes/addons/ingress-deploy.yaml
I0307 18:07:29.962633   94826 ssh_runner.go:352] existence check for /etc/kubernetes/addons/ingress-deploy.yaml: source file and destination file are different sizes
I0307 18:07:29.962695   94826 ssh_runner.go:362] scp /Users/logo/.minikube/addons/ingress-deploy.yaml --> /etc/kubernetes/addons/ingress-deploy.yaml (16490 bytes)
...
I0307 18:07:56.320757   94826 addons.go:348] installing /etc/kubernetes/addons/ingress-deploy.yaml
I0307 18:07:56.320800   94826 ssh_runner.go:362] scp memory --> /etc/kubernetes/addons/ingress-deploy.yaml (15567 bytes)
...
I0307 18:07:56.475502   94826 ssh_runner.go:195] Run: sudo KUBECONFIG=/var/lib/minikube/kubeconfig /var/lib/minikube/binaries/v1.23.3/kubectl apply -f /etc/kubernetes/addons/ingress-deploy.yaml

Thank you for helping.

BTW: kubernetes docs say that hsts: "true" is the default, where as the template set it to hsts: "false" and no other defaults.

Attach the log file

▶ minikube start --driver=ssh --ssh-ip-address=xxx --ssh-user=root --ssh-key=/Users/logo/.ssh/minikube_ed25519 --native-ssh=false --alsologtostderr -v=5 2> start.log

• minikube v1.25.2 auf Darwin 12.2.1 (arm64)
  • MINIKUBE_EXISTING_DOCKER_TLS_VERIFY=1
  • MINIKUBE_EXISTING_DOCKER_HOST=tcp://xxxx:2376
  • MINIKUBE_EXISTING_DOCKER_CERT_PATH=/Users/logo/.docker/machine/machines/default
  • MINIKUBE_ACTIVE_DOCKERD=minikube
• Verwende den Treiber ssh basierend auf dem existierenden Profil
• Starte Control Plane Node minikube in Cluster minikube
• Aktualisiere den laufenden ssh "minikube" bare metal machine ...
• Vorbereiten von Kubernetes v1.23.3 auf Docker 20.10.12...
  • kubelet.housekeeping-interval=5m
• Verifiziere Kubernetes Komponenten...
  • Verwende Image gcr.io/k8s-minikube/storage-provisioner:v5
  • Verwende Image k8s.gcr.io/metrics-server/metrics-server:v0.4.2
  • Verwende Image kubernetesui/dashboard:v2.3.1
  • Verwende Image k8s.gcr.io/ingress-nginx/controller:v1.1.1
  • Verwende Image kubernetesui/metrics-scraper:v1.0.7
  • Verwende Image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1
  • Verwende Image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1
• Verifiziere ingress Addon...
• Addons aktiviert: storage-provisioner, default-storageclass, metrics-server, dashboard, ingress
• Fertig! kubectl ist jetzt für die standardmäßige (default) Verwendung des Clusters "minikube und des Namespaces "default" konfiguriert

I0307 18:07:29.955380   94826 filesync.go:126] Scanning /Users/logo/.minikube/addons for local assets ...
I0307 18:07:29.955727   94826 filesync.go:149] local asset: /Users/logo/.minikube/addons/ingress-deploy.yaml -> ingress-deploy.yaml in /etc/kubernetes/addons
I0307 18:07:29.955770   94826 vm_assets.go:163] NewFileAsset: /Users/logo/.minikube/addons/ingress-deploy.yaml -> /etc/kubernetes/addons/ingress-deploy.yaml
I0307 18:07:29.960826   94826 ssh_runner.go:195] Run: stat -c "%!s(MISSING) %!y(MISSING)" /etc/kubernetes/addons/ingress-deploy.yaml
I0307 18:07:29.962633   94826 ssh_runner.go:352] existence check for /etc/kubernetes/addons/ingress-deploy.yaml: source file and destination file are different sizes
I0307 18:07:29.962695   94826 ssh_runner.go:362] scp /Users/logo/.minikube/addons/ingress-deploy.yaml --> /etc/kubernetes/addons/ingress-deploy.yaml (16490 bytes)
...
I0307 18:07:56.320757   94826 addons.go:348] installing /etc/kubernetes/addons/ingress-deploy.yaml
I0307 18:07:56.320800   94826 ssh_runner.go:362] scp memory --> /etc/kubernetes/addons/ingress-deploy.yaml (15567 bytes)
...
I0307 18:07:56.475502   94826 ssh_runner.go:195] Run: sudo KUBECONFIG=/var/lib/minikube/kubeconfig /var/lib/minikube/binaries/v1.23.3/kubectl apply -f /etc/kubernetes/addons/ingress-deploy.yaml

Operating System

macOS (Default)

Driver

SSH

[RA489]

/kind support

[sharifelgamal]

Yeah this has to do with how addons work. On restart, we reapply the default tempate yamls for the ingress addon, which will indeed wipe out any changes you've made.

The solution here could be to add an entry to minikube addons configure so that we can accept non-default config.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[RA489]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[logopk]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[logopk]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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/test-infra repository.

[logopk]

/reopen

[k8s-ci-robot]

@logopk: Reopened this issue.

In response to this:

/reopen

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/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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/test-infra repository.

[logopk]

please /reopen - this is a hassle.

[logopk]

/reopen

[k8s-ci-robot]

@logopk: Reopened this issue.

In response to this:

/reopen

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/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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/test-infra repository.

[logopk]

/remove-lifecycle rotten

[logopk]

/reopen

[k8s-ci-robot]

@logopk: Reopened this issue.

In response to this:

/reopen

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/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[logopk]

/reopen

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[logopk]

/remove-lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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/test-infra repository.

[logopk]

/remove-lifecycle rotten

[logopk]

/reopen

[k8s-ci-robot]

@logopk: Reopened this issue.

In response to this:

/reopen

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/test-infra repository.