handsome-actor-1155
05/30/2019, 10:55 PMst1
. It seems that both a gp2
AND my st1
storageClasses get created and they are both marked as default
. Is this expected behavior? Is there a specific property I need to set to prevent that from happening?
// Create a VPC for our cluster.
const vpc = new awsx.ec2.Vpc("Kafka-VPC", {numberOfAvailabilityZones: 3});
// Create an EKS cluster with the given configuration.
const cluster = new eks.Cluster("kafka-cluster", {
vpcId: vpc.id,
subnetIds: vpc.privateSubnetIds,
instanceType: instanceType,
desiredCapacity: desiredCapacity,
minSize: minSize,
maxSize: maxSize,
storageClasses: storageClass,
deployDashboard: deployDashboard,
});
white-balloon-205
"@pulumi/eks": "dev"
in your package.json, you should be able to see whether that fix will address this for you.handsome-actor-1155
05/30/2019, 11:04 PM> kubectl get storageclasses
NAME PROVISIONER AGE
gp2 (default) <http://kubernetes.io/aws-ebs|kubernetes.io/aws-ebs> 23m
kafka-cluster-st1-evr2qvmh (default) <http://kubernetes.io/aws-ebs|kubernetes.io/aws-ebs> 21m
Having the gp2
class is fine, just the fact that both are marked as default can cause issues.
I’ll try it out, thanksdev
version of eks and still got both storage classes marked as default
white-balloon-205
(default)
- which would make it hard to change that default. We'll need to look at what we can do about that (and whether that is what's happening here).handsome-actor-1155
05/31/2019, 12:11 AM