Enterprise Kubernetes, delivered

Tectonic ships with CoreOS's signature automated operations, runs multi-cloud, and is the fastest, most secure path to Kubernetes.

AWS: Troubleshooting Installation

Known issues and gotchas in Tectonic installation on AWS

Route53 DNS resolution

An issue arises when a domain's A record resolution is attempted before Route53 publishes the cluster's A record and the NXDOMAIN response is cached in the NCACHE (RFC2308). This negative response may be cached for up to the number of seconds set in the domain's SOA record's TTL. Resolution fails until the negative caching TTL expires. These TTLs are typically large enough to disrupt the installation. The current workaround is to ensure your TTLs are set to a low interval, or to wait for them to expire, then proceed with the installation.

Domain name can't be changed

The domain or subdomain configured for Route53 name service and selected during Tectonic install cannot be easily changed later. If a cluster's domain name needs to change, set up a new cluster with the new domain name and migrate cluster work to it.

License and pull-secret formats

When copying your license and pull-secret from account.coreos.com, be sure to choose the correct format. The license format should be "Raw Format" and the pull-secret should be in the "dockercfg" format.

Safari browser on OSX

Tectonic Installer may fail to download assets.zip file during the install due to a known issue in Safari/Webkit. OSX users are advised to use Firefox or Chrome to use Tectonic Installer on OSX machines.

Community Support Forum

Make sure to check out the community support forum to work through issues, report bugs, identify documentation requirements, or put in feature requests.