Skip to content

Instantly share code, notes, and snippets.

@O1ahmad
Created November 12, 2020 17:14
Show Gist options
  • Select an option

  • Save O1ahmad/0b1b1d29ba7d11b17aef7d875dfd9641 to your computer and use it in GitHub Desktop.

Select an option

Save O1ahmad/0b1b1d29ba7d11b17aef7d875dfd9641 to your computer and use it in GitHub Desktop.
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
------------------------------------------------------------------------
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# kubernetes_storage_class.central1_ssd will be created
+ resource "kubernetes_storage_class" "central1_ssd" {
+ allow_volume_expansion = true
+ id = (known after apply)
+ parameters = {
+ "type" = "pd-ssd"
}
+ reclaim_policy = "Delete"
+ storage_provisioner = "kubernetes.io/gce-pd"
+ volume_binding_mode = "Immediate"
+ metadata {
+ generation = (known after apply)
+ name = "central1-ssd"
+ resource_version = (known after apply)
+ self_link = (known after apply)
+ uid = (known after apply)
}
}
Plan: 1 to add, 0 to change, 0 to destroy.
Warning: Resource targeting is in effect
You are creating a plan with the -target option, which means that the result
of this plan may not represent all of the changes requested by the current
configuration.
The -target option is not for routine use, and is provided only for
exceptional situations such as recovering from errors or mistakes, or when
Terraform specifically suggests to use it as part of an error message.
------------------------------------------------------------------------
Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
------------------------------------------------------------------------
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# kubernetes_storage_class.central1_standard will be created
+ resource "kubernetes_storage_class" "central1_standard" {
+ allow_volume_expansion = true
+ id = (known after apply)
+ parameters = {
+ "type" = "pd-standard"
}
+ reclaim_policy = "Delete"
+ storage_provisioner = "kubernetes.io/gce-pd"
+ volume_binding_mode = "Immediate"
+ metadata {
+ generation = (known after apply)
+ name = "central1-standard"
+ resource_version = (known after apply)
+ self_link = (known after apply)
+ uid = (known after apply)
}
}
Plan: 1 to add, 0 to change, 0 to destroy.
Warning: Resource targeting is in effect
You are creating a plan with the -target option, which means that the result
of this plan may not represent all of the changes requested by the current
configuration.
The -target option is not for routine use, and is provided only for
exceptional situations such as recovering from errors or mistakes, or when
Terraform specifically suggests to use it as part of an error message.
------------------------------------------------------------------------
Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
------------------------------------------------------------------------
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# kubernetes_storage_class.east1_ssd will be created
+ resource "kubernetes_storage_class" "east1_ssd" {
+ allow_volume_expansion = true
+ id = (known after apply)
+ parameters = {
+ "type" = "pd-ssd"
}
+ reclaim_policy = "Delete"
+ storage_provisioner = "kubernetes.io/gce-pd"
+ volume_binding_mode = "Immediate"
+ metadata {
+ generation = (known after apply)
+ name = "east1-ssd"
+ resource_version = (known after apply)
+ self_link = (known after apply)
+ uid = (known after apply)
}
}
Plan: 1 to add, 0 to change, 0 to destroy.
Warning: Resource targeting is in effect
You are creating a plan with the -target option, which means that the result
of this plan may not represent all of the changes requested by the current
configuration.
The -target option is not for routine use, and is provided only for
exceptional situations such as recovering from errors or mistakes, or when
Terraform specifically suggests to use it as part of an error message.
------------------------------------------------------------------------
Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
------------------------------------------------------------------------
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# kubernetes_storage_class.east1_standard will be created
+ resource "kubernetes_storage_class" "east1_standard" {
+ allow_volume_expansion = true
+ id = (known after apply)
+ parameters = {
+ "type" = "pd-standard"
}
+ reclaim_policy = "Delete"
+ storage_provisioner = "kubernetes.io/gce-pd"
+ volume_binding_mode = "Immediate"
+ metadata {
+ generation = (known after apply)
+ name = "east1-standard"
+ resource_version = (known after apply)
+ self_link = (known after apply)
+ uid = (known after apply)
}
}
Plan: 1 to add, 0 to change, 0 to destroy.
Warning: Resource targeting is in effect
You are creating a plan with the -target option, which means that the result
of this plan may not represent all of the changes requested by the current
configuration.
The -target option is not for routine use, and is provided only for
exceptional situations such as recovering from errors or mistakes, or when
Terraform specifically suggests to use it as part of an error message.
------------------------------------------------------------------------
Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
------------------------------------------------------------------------
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# kubernetes_storage_class.east4_ssd will be created
+ resource "kubernetes_storage_class" "east4_ssd" {
+ allow_volume_expansion = true
+ id = (known after apply)
+ parameters = {
+ "type" = "pd-ssd"
}
+ reclaim_policy = "Delete"
+ storage_provisioner = "kubernetes.io/gce-pd"
+ volume_binding_mode = "Immediate"
+ metadata {
+ generation = (known after apply)
+ name = "east4-ssd"
+ resource_version = (known after apply)
+ self_link = (known after apply)
+ uid = (known after apply)
}
}
Plan: 1 to add, 0 to change, 0 to destroy.
Warning: Resource targeting is in effect
You are creating a plan with the -target option, which means that the result
of this plan may not represent all of the changes requested by the current
configuration.
The -target option is not for routine use, and is provided only for
exceptional situations such as recovering from errors or mistakes, or when
Terraform specifically suggests to use it as part of an error message.
------------------------------------------------------------------------
Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
------------------------------------------------------------------------
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# kubernetes_storage_class.east4_standard will be created
+ resource "kubernetes_storage_class" "east4_standard" {
+ allow_volume_expansion = true
+ id = (known after apply)
+ parameters = {
+ "type" = "pd-standard"
}
+ reclaim_policy = "Delete"
+ storage_provisioner = "kubernetes.io/gce-pd"
+ volume_binding_mode = "Immediate"
+ metadata {
+ generation = (known after apply)
+ name = "east4-standard"
+ resource_version = (known after apply)
+ self_link = (known after apply)
+ uid = (known after apply)
}
}
Plan: 1 to add, 0 to change, 0 to destroy.
Warning: Resource targeting is in effect
You are creating a plan with the -target option, which means that the result
of this plan may not represent all of the changes requested by the current
configuration.
The -target option is not for routine use, and is provided only for
exceptional situations such as recovering from errors or mistakes, or when
Terraform specifically suggests to use it as part of an error message.
------------------------------------------------------------------------
Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment