mirror of
https://github.com/openshift/installer.git
synced 2026-02-06 09:47:02 +01:00
examples: Provide tectonic sample config for AWS
This commit is contained in:
committed by
Max Leonard Inden
parent
f678d42dbb
commit
b965bc071a
359
examples/tectonic.aws.yaml
Normal file
359
examples/tectonic.aws.yaml
Normal file
@@ -0,0 +1,359 @@
|
||||
Clusters:
|
||||
- AWS:
|
||||
# (optional) Unique name under which the Amazon S3 bucket will be created. Bucket name must start with a lower case name and is limited to 63 characters.
|
||||
# The Tectonic Installer uses the bucket to store tectonic assets and kubeconfig.
|
||||
# If name is not provided the installer will construct the name using "Name", current AWS region and "BaseDomain"
|
||||
# AssetsS3BucketName:
|
||||
|
||||
# (optional) Extra AWS tags to be applied to created autoscaling group resources.
|
||||
# This is a list of maps having the keys `key`, `value` and `propagate_at_launch`.
|
||||
#
|
||||
# Example: `[ { key = "foo", value = "bar", propagate_at_launch = true } ]`
|
||||
# AutoScalingGroupExtraTags:
|
||||
|
||||
# (optional) AMI override for all nodes. Example: `ami-foobar123`.
|
||||
# EC2AMIOverride:
|
||||
|
||||
Etcd:
|
||||
# Instance size for the etcd node(s). Example: `t2.medium`. Read the [etcd recommended hardware](https:#coreos.com/etcd/docs/latest/op-guide/hardware.html) guide for best performance
|
||||
EC2Type: t2.medium
|
||||
|
||||
# (optional) List of additional security group IDs for etcd nodes.
|
||||
#
|
||||
# Example: `["sg-51530134", "sg-b253d7cc"]`
|
||||
# ExtraSGIDs:
|
||||
|
||||
# (optional) Name of IAM role to use for the instance profiles of etcd nodes.
|
||||
# The name is also the last part of a role's ARN.
|
||||
#
|
||||
# Example:
|
||||
# * Role ARN = arn:aws:iam::123456789012:role/tectonic-installer
|
||||
# * Role Name = tectonic-installer
|
||||
# IAMRoleName:
|
||||
|
||||
RootVolume:
|
||||
# The amount of provisioned IOPS for the root block device of etcd nodes.
|
||||
# Ignored if the volume type is not io1.
|
||||
IOPS: 100
|
||||
|
||||
# The size of the volume in gigabytes for the root block device of etcd nodes.
|
||||
Size: 30
|
||||
|
||||
# The type of volume for the root block device of etcd nodes.
|
||||
Type: gp2
|
||||
|
||||
External:
|
||||
# (optional) List of subnet IDs within an existing VPC to deploy master nodes into.
|
||||
# Required to use an existing VPC and the list must match the AZ count.
|
||||
#
|
||||
# Example: `["subnet-111111", "subnet-222222", "subnet-333333"]`
|
||||
# MasterSubnetIDs:
|
||||
|
||||
# (optional) If set, the given Route53 zone ID will be used as the internal (private) zone.
|
||||
# This zone will be used to create etcd DNS records as well as internal API and internal Ingress records.
|
||||
# If set, no additional private zone will be created.
|
||||
#
|
||||
# Example: `"Z1ILINNUJGTAO1"`
|
||||
# PrivateZone:
|
||||
|
||||
# (optional) ID of an existing VPC to launch nodes into.
|
||||
# If unset a new VPC is created.
|
||||
#
|
||||
# Example: `vpc-123456`
|
||||
# VPCID:
|
||||
|
||||
# (optional) List of subnet IDs within an existing VPC to deploy worker nodes into.
|
||||
# Required to use an existing VPC and the list must match the AZ count.
|
||||
#
|
||||
# Example: `["subnet-111111", "subnet-222222", "subnet-333333"]`
|
||||
# WorkerSubnetIDs:
|
||||
|
||||
# (optional) Extra AWS tags to be applied to created resources.
|
||||
#
|
||||
# Example: `{ "key" = "value", "foo" = "bar" }`
|
||||
# ExtraTags:
|
||||
|
||||
# (optional) Name of IAM role to use to access AWS in order to deploy the Tectonic Cluster.
|
||||
# The name is also the full role's ARN.
|
||||
#
|
||||
# Example:
|
||||
# * Role ARN = arn:aws:iam::123456789012:role/tectonic-installer
|
||||
# InstallerRole:
|
||||
|
||||
Master:
|
||||
# (optional) This configures master availability zones and their corresponding subnet CIDRs directly.
|
||||
#
|
||||
# Example:
|
||||
# `{ eu-west-1a = "10.0.0.0/20", eu-west-1b = "10.0.16.0/20" }`
|
||||
# CustomSubnets:
|
||||
|
||||
# Instance size for the master node(s). Example: `t2.medium`.
|
||||
EC2Type: t2.medium
|
||||
|
||||
# (optional) List of additional security group IDs for master nodes.
|
||||
#
|
||||
# Example: `["sg-51530134", "sg-b253d7cc"]`
|
||||
# ExtraSGIDs:
|
||||
|
||||
# (optional) Name of IAM role to use for the instance profiles of master nodes.
|
||||
# The name is also the last part of a role's ARN.
|
||||
#
|
||||
# Example:
|
||||
# * Role ARN = arn:aws:iam::123456789012:role/tectonic-installer
|
||||
# * Role Name = tectonic-installer
|
||||
# IAMRoleName:
|
||||
|
||||
RootVolume:
|
||||
# The amount of provisioned IOPS for the root block device of master nodes.
|
||||
# Ignored if the volume type is not io1.
|
||||
IOPS: 100
|
||||
|
||||
# The size of the volume in gigabytes for the root block device of master nodes.
|
||||
Size: 30
|
||||
|
||||
# The type of volume for the root block device of master nodes.
|
||||
Type: gp2
|
||||
|
||||
# (optional) If set to true, create private-facing ingress resources (ELB, A-records).
|
||||
# If set to false, no private-facing ingress resources will be provisioned and all DNS records will be created in the public Route53 zone.
|
||||
# PrivateEndpoints: true
|
||||
|
||||
# (optional) This declares the AWS credentials profile to use.
|
||||
# Profile: default
|
||||
|
||||
# (optional) If set to true, create public-facing ingress resources (ELB, A-records).
|
||||
# If set to false, no public-facing ingress resources will be created.
|
||||
# PublicEndpoints: true
|
||||
|
||||
# The target AWS region for the cluster.
|
||||
Region: eu-west-1
|
||||
|
||||
# Name of an SSH key located within the AWS region. Example: coreos-user.
|
||||
SSHKey:
|
||||
|
||||
# Block of IP addresses used by the VPC.
|
||||
# This should not overlap with any other networks, such as a private datacenter connected via Direct Connect.
|
||||
VPCCIDRBlock: 10.0.0.0/16
|
||||
|
||||
Worker:
|
||||
# (optional) This configures worker availability zones and their corresponding subnet CIDRs directly.
|
||||
#
|
||||
# Example: `{ eu-west-1a = "10.0.64.0/20", eu-west-1b = "10.0.80.0/20" }`
|
||||
# CustomSubnets:
|
||||
|
||||
# Instance size for the worker node(s). Example: `t2.medium`.
|
||||
EC2Type: t2.medium
|
||||
|
||||
# (optional) List of additional security group IDs for worker nodes.
|
||||
#
|
||||
# Example: `["sg-51530134", "sg-b253d7cc"]`
|
||||
# ExtraSGIDs:
|
||||
|
||||
# (optional) Name of IAM role to use for the instance profiles of worker nodes.
|
||||
# The name is also the last part of a role's ARN.
|
||||
#
|
||||
# Example:
|
||||
# * Role ARN = arn:aws:iam::123456789012:role/tectonic-installer
|
||||
# * Role Name = tectonic-installer
|
||||
# IAMRoleName:
|
||||
|
||||
# (optional) List of ELBs to attach all worker instances to.
|
||||
# This is useful for exposing NodePort services via load-balancers managed separately from the cluster.
|
||||
#
|
||||
# Example:
|
||||
# * `["ingress-nginx"]`
|
||||
# LoadBalancers:
|
||||
|
||||
RootVolume:
|
||||
# The amount of provisioned IOPS for the root block device of worker nodes.
|
||||
# Ignored if the volume type is not io1.
|
||||
IOPS: 100
|
||||
|
||||
# The size of the volume in gigabytes for the root block device of worker nodes.
|
||||
Size: 30
|
||||
|
||||
# The type of volume for the root block device of worker nodes.
|
||||
Type: gp2
|
||||
|
||||
# The base DNS domain of the cluster. It must NOT contain a trailing period. Some
|
||||
# DNS providers will automatically add this if necessary.
|
||||
#
|
||||
# Example: `openstack.dev.coreos.systems`.
|
||||
#
|
||||
# Note: This field MUST be set manually prior to creating the cluster.
|
||||
# This applies only to cloud platforms.
|
||||
#
|
||||
# [Azure-specific NOTE]
|
||||
# To use Azure-provided DNS, `BaseDomain` should be set to `""`
|
||||
# If using DNS records, ensure that `BaseDomain` is set to a properly configured external DNS zone.
|
||||
# Instructions for configuring delegated domains for Azure DNS can be found here: https://docs.microsoft.com/en-us/azure/dns/dns-delegate-domain-azure-dns
|
||||
BaseDomain:
|
||||
|
||||
CA:
|
||||
# (optional) The content of the PEM-encoded CA certificate, used to generate Tectonic Console's server certificate.
|
||||
# If left blank, a CA certificate will be automatically generated.
|
||||
# Cert:
|
||||
|
||||
# (optional) The content of the PEM-encoded CA key, used to generate Tectonic Console's server certificate.
|
||||
# This field is mandatory if `ca_cert` is set.
|
||||
# Key:
|
||||
|
||||
# (optional) The algorithm used to generate ca_key.
|
||||
# The default value is currently recommended.
|
||||
# This field is mandatory if `ca_cert` is set.
|
||||
# KeyAlg: RSA
|
||||
|
||||
ContainerLinux:
|
||||
# (optional) The Container Linux update channel.
|
||||
#
|
||||
# Examples: `stable`, `beta`, `alpha`
|
||||
# Channel: stable
|
||||
|
||||
# The Container Linux version to use. Set to `latest` to select the latest available version for the selected update channel.
|
||||
#
|
||||
# Examples: `latest`, `1465.6.0`
|
||||
Version: latest
|
||||
|
||||
# (optional) A list of PEM encoded CA files that will be installed in /etc/ssl/certs on etcd, master, and worker nodes.
|
||||
# CustomCAPEMList:
|
||||
|
||||
DDNS:
|
||||
Key:
|
||||
# (optional) This only applies if you use the modules/dns/ddns module.
|
||||
#
|
||||
# Specifies the RFC2136 Dynamic DNS server key algorithm.
|
||||
# Algorithm:
|
||||
|
||||
# (optional) This only applies if you use the modules/dns/ddns module.
|
||||
#
|
||||
# Specifies the RFC2136 Dynamic DNS server key name.
|
||||
# Name:
|
||||
|
||||
# (optional) This only applies if you use the modules/dns/ddns module.
|
||||
#
|
||||
# Specifies the RFC2136 Dynamic DNS server key secret.
|
||||
# Secret:
|
||||
|
||||
# (optional) This only applies if you use the modules/dns/ddns module.
|
||||
#
|
||||
# Specifies the RFC2136 Dynamic DNS server IP/host to register IP addresses to.
|
||||
# Server:
|
||||
|
||||
# (optional) DNS prefix used to construct the console and API server endpoints.
|
||||
# DNSName:
|
||||
|
||||
Etcd:
|
||||
# The number of etcd nodes to be created.
|
||||
# If set to zero, the count of etcd nodes will be determined automatically.
|
||||
#
|
||||
# Note: This is not supported on bare metal.
|
||||
Count: 0
|
||||
|
||||
External:
|
||||
# (optional) The path of the file containing the CA certificate for TLS communication with etcd.
|
||||
#
|
||||
# Note: This works only when used in conjunction with an external etcd cluster.
|
||||
# If set, the variable `Servers` must also be set.
|
||||
# CACertPath: /dev/null
|
||||
|
||||
# (optional) The path of the file containing the client certificate for TLS communication with etcd.
|
||||
#
|
||||
# Note: This works only when used in conjunction with an external etcd cluster.
|
||||
# If set, the variables `Servers`, `CACertPath`, and `ClientKeyPath` must also be set.
|
||||
# ClientCertPath: /dev/null
|
||||
|
||||
# (optional) The path of the file containing the client key for TLS communication with etcd.
|
||||
#
|
||||
# Note: This works only when used in conjunction with an external etcd cluster.
|
||||
# If set, the variables `servers`, `CACertPath`, and `ClientCertPath` must also be set.
|
||||
# ClientKeyPath: /dev/null
|
||||
|
||||
# (optional) List of external etcd v3 servers to connect with (hostnames/IPs only).
|
||||
# Needs to be set if using an external etcd cluster.
|
||||
# Note: If this variable is defined, the installer will not create self-signed certs.
|
||||
# To provide a CA certificate to trust the etcd servers, set "CACertPath".
|
||||
#
|
||||
# Example: `["etcd1", "etcd2", "etcd3"]`
|
||||
# Servers:
|
||||
|
||||
ISCSI:
|
||||
# (optional) Start iscsid.service to enable iscsi volume attachment.
|
||||
# Enabled: false
|
||||
|
||||
# The path to the tectonic licence file.
|
||||
# You can download the Tectonic license file from your Account overview page at [1].
|
||||
#
|
||||
# [1] https://account.coreos.com/overview
|
||||
LicensePath:
|
||||
|
||||
Master:
|
||||
# The number of master nodes to be created.
|
||||
# This applies only to cloud platforms.
|
||||
Count: 1
|
||||
|
||||
# The name of the cluster.
|
||||
# If used in a cloud-environment, this will be prepended to `BaseDomain` resulting in the URL to the Tectonic console.
|
||||
#
|
||||
# Note: This field MUST be set manually prior to creating the cluster.
|
||||
# Warning: Special characters in the name like '.' may cause errors on OpenStack platforms due to resource name constraints.
|
||||
Name:
|
||||
|
||||
Networking:
|
||||
# (optional) Configures the network to be used in Tectonic. One of the following values can be used:
|
||||
#
|
||||
# - "flannel": enables overlay networking only. This is implemented by flannel using VXLAN.
|
||||
#
|
||||
# - "canal": enables overlay networking including network policy. Overlay is implemented by flannel using VXLAN. Network policy is implemented by Calico.
|
||||
#
|
||||
# - "calico-ipip": [ALPHA] enables BGP based networking. Routing and network policy is implemented by Calico. Note this has been tested on baremetal installations only.
|
||||
#
|
||||
# - "none": disables the installation of any Pod level networking layer provided by Tectonic. By setting this value, users are expected to deploy their own solution to enable network connectivity for Pods and Services.
|
||||
# Type: canal
|
||||
|
||||
# (optional) This declares the MTU used by Calico.
|
||||
# MTU:
|
||||
|
||||
# (optional) This declares the IP range to assign Kubernetes service cluster IPs in CIDR notation.
|
||||
# The maximum size of this IP range is /12
|
||||
# ServiceCIDR: 10.3.0.0/16
|
||||
|
||||
# (optional) This declares the IP range to assign Kubernetes pod IPs in CIDR notation.
|
||||
# PodCIDR: 10.2.0.0/16
|
||||
|
||||
Proxy:
|
||||
# (optional) HTTP proxy address.
|
||||
#
|
||||
# Example: `http://myproxy.example.com`
|
||||
# HTTP:
|
||||
|
||||
# (optional) HTTPS proxy address.
|
||||
#
|
||||
# Example: `http://myproxy.example.com`
|
||||
# HTTPS:
|
||||
|
||||
# (optional) List of local endpoints that will not use HTTP proxy.
|
||||
#
|
||||
# Example: `["127.0.0.1","localhost",".example.com","10.3.0.1"]`
|
||||
# No:
|
||||
|
||||
# The path the pull secret file in JSON format.
|
||||
# This is known to be a "Docker pull secret" as produced by the docker login [1] command.
|
||||
# A sample JSON content is shown in [2].
|
||||
# You can download the pull secret from your Account overview page at [3].
|
||||
#
|
||||
# [1] https://docs.docker.com/engine/reference/commandline/login/
|
||||
#
|
||||
# [2] https://coreos.com/os/docs/latest/registry-authentication.html#manual-registry-auth-setup
|
||||
#
|
||||
# [3] https://account.coreos.com/overview
|
||||
PullSecretPath:
|
||||
|
||||
# Validity period of the self-signed certificates (in hours).
|
||||
# Default is 3 years.
|
||||
# This setting is ignored if user provided certificates are used.
|
||||
TLSValidityPeriod: 26280
|
||||
|
||||
Worker:
|
||||
# The number of worker nodes to be created.
|
||||
# This applies only to cloud platforms.
|
||||
Count: 3
|
||||
@@ -61,7 +61,7 @@ type containerLinux struct {
|
||||
}
|
||||
|
||||
type ddns struct {
|
||||
Key ddnsKey `yaml:"Secret"`
|
||||
Key ddnsKey `yaml:"Key"`
|
||||
Server string `yaml:"Secret"`
|
||||
}
|
||||
|
||||
@@ -78,7 +78,7 @@ type etcd struct {
|
||||
|
||||
type etcdExternal struct {
|
||||
CACertPath string `yaml:"CACertPath"`
|
||||
ClientCertPath string `yam:"ClientCertPath"`
|
||||
ClientCertPath string `yaml:"ClientCertPath"`
|
||||
ClientKeyPath string `yaml:"ClientKeyPath"`
|
||||
Servers []string `yaml:"Servers"`
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user