Known issues

[alexsomesan]

trafficstars

The following issues are known to exist:

Be assured that solutions are being explored for them.

• Empty blocks in the manifest may cause inconsistent state after apply Description: Manifests containing empty blocks (e.g. foo = {}) may cause the following error after apply. Workaround: Empty blocks should be omitted from the manifest configuration unless they have a special significance. So far, the only confirmed case of such a special significance is the status = {} attribute inside the subresources section of a Custom Resource Definition. All others should be omitted.

• The protocol attribute of a ports element in Service or Container is resource is required Description: Bug in Kubernetes (https://github.com/kubernetes/kubernetes/issues/92332 and https://github.com/kubernetes-sigs/structured-merge-diff/issues/130) - will be fixed in 1.21 Not setting the protocol attribute in a Service's or Container's ports list will result in the following error: failed to create typed patch object: .spec.ports: element 0: associative list with keys has an element that omits key field "protocol" (and doesn't have default value) Workaround: Set the protocol attribute to TCP when no other value specified

• Setting some attributes to their default value may cause inconsistent state after apply Description: On some attributes, setting them to their default value will result in an error message after apply claiming inconsistent state Workaround: Do not include attributes with default values in the manifest as a rule. They have no effect on the resulting resource.

[redeux]

Another known (non-bug) issue. Provider >=v0.3.0 requires Terraform >=0.14.8 or >=0.15.0-beta1