Documentation ¶
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func IsInvalidConfig ¶
IsInvalidConfig asserts invalidConfigError.
Types ¶
type Config ¶
type Config struct { HostAWSConfig clientaws.Config K8sClient kubernetes.Interface Logger micrologger.Logger Route53Enabled bool }
type Resource ¶
type Resource struct {
// contains filtered or unexported fields
}
cluster_id.k8s.installation.eu-central-1.aws.gigantic.io (byoc tenant account) ├── A api.cluster_id.k8s.installation.eu-central-1.aws.gigantic.io └── A ingress.cluster_id.k8s.installation.eu-central-1.aws.gigantic.io
NOTE: In the code below k8s.installation.eu-central-1.aws.gigantic.io zone is called "intermediate" and cluster_id.k8s.installation.eu-central-1.aws.gigantic.io zone is called "final". This resource *only* ensures we have delegation from the intermediate zone to the final zone, but only if the intermediate zone exists.
After everything is fully migrated the DNS layout should look like:
installation.eu-central-1.aws.gigantic.io (control plane account) ├── NS k8s.installation.eu-central-1.aws.gigantic.io (default guest account) └── NS cluster_id.k8s.installation.eu-central-1.aws.gigantic.io (byoc guest account) k8s.installation.eu-central-1.aws.gigantic.io (default guest account) └── NS cluster_id.k8s.installation.eu-central-1.aws.gigantic.io (byoc guest account) cluster_id.k8s.installation.eu-central-1.aws.gigantic.io (byoc guest account) ├── A api.cluster_id.k8s.installation.eu-central-1.aws.gigantic.io └── A ingress.cluster_id.k8s.installation.eu-central-1.aws.gigantic.io
At this point we should be fine with removing k8s.installation.eu-central-1.aws.gigantic.io NS record from installation.eu-central-1.aws.gigantic.io zone. Then after a couple of days when delegation propagates and DNS caches are refreshed we can delete k8s.installation.eu-central-1.aws.gigantic.io zone from the default guest account.
NOTE: To complete full migration we need to start reconciling "hostpost" CloudFormation stack. This stack is responsible for creating cluster_id.k8s.installation.eu-central-1.aws.gigantic.io delegation in the installation.eu-central-1.aws.gigantic.io. Till this happens this resource cannot be deleted.
See https://github.com/giantswarm/aws-operator/pull/1373.