search

armory / minnaker

Spinnaker on Lightweight Kubernetes (K3s)
Apache License 2.0
145 stars 53 forks source link

Timeout with AWS EC2 install on ap-southeast-2 Australia type: m4.large #35

Closed aleon1220 closed 4 years ago

aleon1220 commented 4 years ago

Installation fails and error of timeout is shown when installing spinnaker OSS in AWS EC2 type m4.large.

Instance Details: 2 CPUs 8192 Memory 60 GB Disk

It meets the requirements but it got stuck during the installation process.

Instance type | Instance family | Instance size | Availability zones | Free-Tier eligible | Bare metal | Hypervisor | vCPUs | Architecture | Cores | Valid cores | Threads per core | Valid threads per core | Sustained clock speed (GHz) | Memory (MiB) | Storage (GB) | Local instance storage | Storage type | Storage disk count | EBS encryption support | EBS optimization support | Network performance | ENA support | Maximum number of network interfaces | IPv4 addresses per interface | IPv6 addresses per interface | IPv6 support | Supported placement group strategies | GPUs | FPGAs | Auto Recovery support | Supported root devices | Dedicated Host support | On-Demand Hibernation support | Burstable Performance support | Current generation | On-Demand Linux pricing | On-Demand Windows pricing
-- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | --
m4.large | m4 | large | ap-southeast-2a, ap-southeast-2b, ap-southeast-2c | false | false | xen | 2 | x86_64 | 1 | 1 | 2 | 1,2 | 2.4 | 8192 | - | - | - | - | supported | default | Moderate | unsupported | 2 | 10 | 10 | true | partition, cluster, spread | - | - | true | - | true | true | - | true | 0.125 USD per Hour | 0.217 USD per Hour
-- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | --
justinrlee commented 4 years ago

What error are you seeing?

justinrlee commented 4 years ago

Usually occurs when you use the wrong IP address or public endpoint

aleon1220 commented 4 years ago

Yes an installation error came up when installing in EC2 instance m4.large for Sydney Region. I just used the following Instance t3a.xlarge and is running smoothly.

aleon1220 commented 4 years ago

If i spot this issue again i will report it. Maybe it was a just once in a lifetime failure. Using a more powerful instance will resolve it.