Invalid spec selector after upgrading helm template

0

I've upgraded helm templates (by hand)

Fragment of previous depoloyment.yaml:

apiVersion: apps/v1beta2 kind: Deployment metadata:   name: {{ template "measurement-collector.fullname" . }}   labels:

    app: {{ template "measurement-collector.name" . }}

    chart: {{ template "measurement-collector.chart" . }}

    release: {{ .Release.Name }}

    heritage: {{ .Release.Service }} spec:   replicas: {{ .Values.replicaCount }}   selector:

    matchLabels:

      app: {{ template "measurement-collector.name" . }}

      release: {{ .Release.Name }}

New one:

apiVersion: apps/v1beta2

kind: Deployment

metadata:

  name: {{ include "measurement-collector.fullname" . }}

  labels:

    app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

    helm.sh/chart: {{ include "measurement-collector.chart" . }}

    app.kubernetes.io/instance: {{ .Release.Name }}

    app.kubernetes.io/managed-by: {{ .Release.Service }}

spec:

  replicas: {{ .Values.replicaCount }}

  selector:

    matchLabels:

      app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

      app.kubernetes.io/instance: {{ .Release.Name }}

new service.yaml:

  name: {{ include "measurement-collector.fullname" . }}

  labels:

    app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

    helm.sh/chart: {{ include "measurement-collector.chart" . }}

    app.kubernetes.io/instance: {{ .Release.Name }}

    app.kubernetes.io/managed-by: {{ .Release.Service }}

spec:

  type: {{ .Values.service.type }}

  ports:

      protocol: TCP

      name: http

  selector:

    app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

    app.kubernetes.io/instance: {{ .Release.Name }}

Then after running: helm upgrade -i measurement-collector chart/measurement-collector --namespace prod --wait

I get:

Error: UPGRADE FAILED: Deployment.apps "measurement-collector" is invalid: spec.selector: Invalid value: 

v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/name":"measurement-collector", "app.kubernetes.io/instance":"measurement-collector"},         

MatchExpressions:v1.LabelSelectorRequirement(nil)}: field is immutable

kubernetes kubernetes-helm

share|improve this question

asked Jan 1 at 19:19

pixelpixel

9,9102190145

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  So the names of the labels have changed. That's tricky if you need to do a straight upgrade of the release - see github.com/helm/helm/issues/2494 and github.com/kubernetes/kubernetes/issues/26202
  
  – Ryan Dawson
  Jan 1 at 19:36
  

  
  
  
  

add a comment | 

0

I've upgraded helm templates (by hand)

Fragment of previous depoloyment.yaml:

apiVersion: apps/v1beta2 kind: Deployment metadata:   name: {{ template "measurement-collector.fullname" . }}   labels:

    app: {{ template "measurement-collector.name" . }}

    chart: {{ template "measurement-collector.chart" . }}

    release: {{ .Release.Name }}

    heritage: {{ .Release.Service }} spec:   replicas: {{ .Values.replicaCount }}   selector:

    matchLabels:

      app: {{ template "measurement-collector.name" . }}

      release: {{ .Release.Name }}

New one:

apiVersion: apps/v1beta2

kind: Deployment

metadata:

  name: {{ include "measurement-collector.fullname" . }}

  labels:

    app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

    helm.sh/chart: {{ include "measurement-collector.chart" . }}

    app.kubernetes.io/instance: {{ .Release.Name }}

    app.kubernetes.io/managed-by: {{ .Release.Service }}

spec:

  replicas: {{ .Values.replicaCount }}

  selector:

    matchLabels:

      app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

      app.kubernetes.io/instance: {{ .Release.Name }}

new service.yaml:

  name: {{ include "measurement-collector.fullname" . }}

  labels:

    app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

    helm.sh/chart: {{ include "measurement-collector.chart" . }}

    app.kubernetes.io/instance: {{ .Release.Name }}

    app.kubernetes.io/managed-by: {{ .Release.Service }}

spec:

  type: {{ .Values.service.type }}

  ports:

      protocol: TCP

      name: http

  selector:

    app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

    app.kubernetes.io/instance: {{ .Release.Name }}

Then after running: helm upgrade -i measurement-collector chart/measurement-collector --namespace prod --wait

I get:

Error: UPGRADE FAILED: Deployment.apps "measurement-collector" is invalid: spec.selector: Invalid value: 

v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/name":"measurement-collector", "app.kubernetes.io/instance":"measurement-collector"},         

MatchExpressions:v1.LabelSelectorRequirement(nil)}: field is immutable

kubernetes kubernetes-helm

share|improve this question

asked Jan 1 at 19:19

pixelpixel

9,9102190145

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  So the names of the labels have changed. That's tricky if you need to do a straight upgrade of the release - see github.com/helm/helm/issues/2494 and github.com/kubernetes/kubernetes/issues/26202
  
  – Ryan Dawson
  Jan 1 at 19:36
  

  
  
  
  

add a comment | 

0

0

0

I've upgraded helm templates (by hand)

Fragment of previous depoloyment.yaml:

apiVersion: apps/v1beta2 kind: Deployment metadata:   name: {{ template "measurement-collector.fullname" . }}   labels:

    app: {{ template "measurement-collector.name" . }}

    chart: {{ template "measurement-collector.chart" . }}

    release: {{ .Release.Name }}

    heritage: {{ .Release.Service }} spec:   replicas: {{ .Values.replicaCount }}   selector:

    matchLabels:

      app: {{ template "measurement-collector.name" . }}

      release: {{ .Release.Name }}

New one:

apiVersion: apps/v1beta2

kind: Deployment

metadata:

  name: {{ include "measurement-collector.fullname" . }}

  labels:

    app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

    helm.sh/chart: {{ include "measurement-collector.chart" . }}

    app.kubernetes.io/instance: {{ .Release.Name }}

    app.kubernetes.io/managed-by: {{ .Release.Service }}

spec:

  replicas: {{ .Values.replicaCount }}

  selector:

    matchLabels:

      app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

      app.kubernetes.io/instance: {{ .Release.Name }}

new service.yaml:

  name: {{ include "measurement-collector.fullname" . }}

  labels:

    app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

    helm.sh/chart: {{ include "measurement-collector.chart" . }}

    app.kubernetes.io/instance: {{ .Release.Name }}

    app.kubernetes.io/managed-by: {{ .Release.Service }}

spec:

  type: {{ .Values.service.type }}

  ports:

      protocol: TCP

      name: http

  selector:

    app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

    app.kubernetes.io/instance: {{ .Release.Name }}

Then after running: helm upgrade -i measurement-collector chart/measurement-collector --namespace prod --wait

I get:

Error: UPGRADE FAILED: Deployment.apps "measurement-collector" is invalid: spec.selector: Invalid value: 

v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/name":"measurement-collector", "app.kubernetes.io/instance":"measurement-collector"},         

MatchExpressions:v1.LabelSelectorRequirement(nil)}: field is immutable

kubernetes kubernetes-helm

share|improve this question

asked Jan 1 at 19:19

pixelpixel

9,9102190145

I've upgraded helm templates (by hand)

Fragment of previous depoloyment.yaml:

apiVersion: apps/v1beta2 kind: Deployment metadata:   name: {{ template "measurement-collector.fullname" . }}   labels:

    app: {{ template "measurement-collector.name" . }}

    chart: {{ template "measurement-collector.chart" . }}

    release: {{ .Release.Name }}

    heritage: {{ .Release.Service }} spec:   replicas: {{ .Values.replicaCount }}   selector:

    matchLabels:

      app: {{ template "measurement-collector.name" . }}

      release: {{ .Release.Name }}

New one:

apiVersion: apps/v1beta2

kind: Deployment

metadata:

  name: {{ include "measurement-collector.fullname" . }}

  labels:

    app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

    helm.sh/chart: {{ include "measurement-collector.chart" . }}

    app.kubernetes.io/instance: {{ .Release.Name }}

    app.kubernetes.io/managed-by: {{ .Release.Service }}

spec:

  replicas: {{ .Values.replicaCount }}

  selector:

    matchLabels:

      app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

      app.kubernetes.io/instance: {{ .Release.Name }}

new service.yaml:

  name: {{ include "measurement-collector.fullname" . }}

  labels:

    app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

    helm.sh/chart: {{ include "measurement-collector.chart" . }}

    app.kubernetes.io/instance: {{ .Release.Name }}

    app.kubernetes.io/managed-by: {{ .Release.Service }}

spec:

  type: {{ .Values.service.type }}

  ports:

      protocol: TCP

      name: http

  selector:

    app.kubernetes.io/name: {{ include "measurement-collector.name" . }}

    app.kubernetes.io/instance: {{ .Release.Name }}

Then after running: helm upgrade -i measurement-collector chart/measurement-collector --namespace prod --wait

I get:

Error: UPGRADE FAILED: Deployment.apps "measurement-collector" is invalid: spec.selector: Invalid value: 

v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/name":"measurement-collector", "app.kubernetes.io/instance":"measurement-collector"},         

MatchExpressions:v1.LabelSelectorRequirement(nil)}: field is immutable

kubernetes kubernetes-helm

kubernetes kubernetes-helm

share|improve this question

asked Jan 1 at 19:19

pixelpixel

9,9102190145

share|improve this question

asked Jan 1 at 19:19

pixelpixel

9,9102190145

share|improve this question

share|improve this question

asked Jan 1 at 19:19

pixelpixel

9,9102190145

asked Jan 1 at 19:19

pixelpixel

9,9102190145

asked Jan 1 at 19:19

pixelpixel

9,9102190145

9,9102190145

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  So the names of the labels have changed. That's tricky if you need to do a straight upgrade of the release - see github.com/helm/helm/issues/2494 and github.com/kubernetes/kubernetes/issues/26202
  
  – Ryan Dawson
  Jan 1 at 19:36
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  So the names of the labels have changed. That's tricky if you need to do a straight upgrade of the release - see github.com/helm/helm/issues/2494 and github.com/kubernetes/kubernetes/issues/26202
  
  – Ryan Dawson
  Jan 1 at 19:36
  

  
  
  
  

1

1

So the names of the labels have changed. That's tricky if you need to do a straight upgrade of the release - see github.com/helm/helm/issues/2494 and github.com/kubernetes/kubernetes/issues/26202

– Ryan Dawson
Jan 1 at 19:36

So the names of the labels have changed. That's tricky if you need to do a straight upgrade of the release - see github.com/helm/helm/issues/2494 and github.com/kubernetes/kubernetes/issues/26202

– Ryan Dawson
Jan 1 at 19:36

add a comment | 

1 Answer
1

active

oldest

votes

1

If you change the selector label, then you will need to purge the release first before deploying.

share|improve this answer

answered Mar 1 at 13:01

TigerBearTigerBear

512419

add a comment | 

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

Thanks for contributing an answer to Stack Overflow!

• Please be sure to answer the question. Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.


• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53998259%2finvalid-spec-selector-after-upgrading-helm-template%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

active

oldest

votes

active

oldest

votes

1

If you change the selector label, then you will need to purge the release first before deploying.

share|improve this answer

answered Mar 1 at 13:01

TigerBearTigerBear

512419

add a comment | 

1

If you change the selector label, then you will need to purge the release first before deploying.

share|improve this answer

answered Mar 1 at 13:01

TigerBearTigerBear

512419

add a comment | 

1

1

1

If you change the selector label, then you will need to purge the release first before deploying.

share|improve this answer

answered Mar 1 at 13:01

TigerBearTigerBear

512419

If you change the selector label, then you will need to purge the release first before deploying.

share|improve this answer

answered Mar 1 at 13:01

TigerBearTigerBear

512419

share|improve this answer

share|improve this answer

answered Mar 1 at 13:01

TigerBearTigerBear

512419

answered Mar 1 at 13:01

TigerBearTigerBear

512419

answered Mar 1 at 13:01

TigerBearTigerBear

512419

512419

add a comment | 

add a comment | 

Thanks for contributing an answer to Stack Overflow!

• Please be sure to answer the question. Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.


• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

• Please be sure to answer the question. Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.


• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53998259%2finvalid-spec-selector-after-upgrading-helm-template%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

Name

Name

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Name

Name

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

This page is only for reference, If you need detailed information, please check here