Terraform error when updating kubernetes_deployment
I'm new to Terraform, and using it to create a Kubernetes cluster on GKE. I also want to create a Kubernetes deployment using the kubernetes_deployment resource type. This works perfectly, until I make a change to the deployment and run 'terraform apply' again. This results in the following error:
kubernetes_deployment.example: replicationcontrollers "terraform-example" not found
It looks like the Kubernetes provider starts looking for a replication controller to modify instead of a deployment. Am I doing something wrong, or might this be a bug in the provider?
I'm trying this with the following example: https://www.terraform.io/docs/providers/kubernetes/r/deployment.html
Thanks,
Daniel
add a comment |
I'm new to Terraform, and using it to create a Kubernetes cluster on GKE. I also want to create a Kubernetes deployment using the kubernetes_deployment resource type. This works perfectly, until I make a change to the deployment and run 'terraform apply' again. This results in the following error:
kubernetes_deployment.example: replicationcontrollers "terraform-example" not found
It looks like the Kubernetes provider starts looking for a replication controller to modify instead of a deployment. Am I doing something wrong, or might this be a bug in the provider?
I'm trying this with the following example: https://www.terraform.io/docs/providers/kubernetes/r/deployment.html
Thanks,
Daniel
add a comment |
I'm new to Terraform, and using it to create a Kubernetes cluster on GKE. I also want to create a Kubernetes deployment using the kubernetes_deployment resource type. This works perfectly, until I make a change to the deployment and run 'terraform apply' again. This results in the following error:
kubernetes_deployment.example: replicationcontrollers "terraform-example" not found
It looks like the Kubernetes provider starts looking for a replication controller to modify instead of a deployment. Am I doing something wrong, or might this be a bug in the provider?
I'm trying this with the following example: https://www.terraform.io/docs/providers/kubernetes/r/deployment.html
Thanks,
Daniel
I'm new to Terraform, and using it to create a Kubernetes cluster on GKE. I also want to create a Kubernetes deployment using the kubernetes_deployment resource type. This works perfectly, until I make a change to the deployment and run 'terraform apply' again. This results in the following error:
kubernetes_deployment.example: replicationcontrollers "terraform-example" not found
It looks like the Kubernetes provider starts looking for a replication controller to modify instead of a deployment. Am I doing something wrong, or might this be a bug in the provider?
I'm trying this with the following example: https://www.terraform.io/docs/providers/kubernetes/r/deployment.html
Thanks,
Daniel
asked Nov 11 at 16:25
Daniel
3601516
3601516
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It looks like a but there's already an issue open here.
You can also see a gist with the logs here.
A deployment creates and managers a ReplicaSet and not a ReplicationController. A replication controller is the older Kubernetes way of managing replicas and you may still some K8s resource definitions out there, and it's still supported. However, a lot of new management of stateless replicas has been centered mostly around Deployments/ReplicaSets.
This explains it, many thanks!
– Daniel
Nov 12 at 7:40
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
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53250746%2fterraform-error-when-updating-kubernetes-deployment%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It looks like a but there's already an issue open here.
You can also see a gist with the logs here.
A deployment creates and managers a ReplicaSet and not a ReplicationController. A replication controller is the older Kubernetes way of managing replicas and you may still some K8s resource definitions out there, and it's still supported. However, a lot of new management of stateless replicas has been centered mostly around Deployments/ReplicaSets.
This explains it, many thanks!
– Daniel
Nov 12 at 7:40
add a comment |
It looks like a but there's already an issue open here.
You can also see a gist with the logs here.
A deployment creates and managers a ReplicaSet and not a ReplicationController. A replication controller is the older Kubernetes way of managing replicas and you may still some K8s resource definitions out there, and it's still supported. However, a lot of new management of stateless replicas has been centered mostly around Deployments/ReplicaSets.
This explains it, many thanks!
– Daniel
Nov 12 at 7:40
add a comment |
It looks like a but there's already an issue open here.
You can also see a gist with the logs here.
A deployment creates and managers a ReplicaSet and not a ReplicationController. A replication controller is the older Kubernetes way of managing replicas and you may still some K8s resource definitions out there, and it's still supported. However, a lot of new management of stateless replicas has been centered mostly around Deployments/ReplicaSets.
It looks like a but there's already an issue open here.
You can also see a gist with the logs here.
A deployment creates and managers a ReplicaSet and not a ReplicationController. A replication controller is the older Kubernetes way of managing replicas and you may still some K8s resource definitions out there, and it's still supported. However, a lot of new management of stateless replicas has been centered mostly around Deployments/ReplicaSets.
answered Nov 11 at 19:54
Rico
26k94864
26k94864
This explains it, many thanks!
– Daniel
Nov 12 at 7:40
add a comment |
This explains it, many thanks!
– Daniel
Nov 12 at 7:40
This explains it, many thanks!
– Daniel
Nov 12 at 7:40
This explains it, many thanks!
– Daniel
Nov 12 at 7:40
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53250746%2fterraform-error-when-updating-kubernetes-deployment%23new-answer', 'question_page');
}
);
Post as a guest
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
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
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
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown