-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Elasticache controller - make usage of SecurityGroup Ref. #1860
Elasticache controller - make usage of SecurityGroup Ref. #1860
Comments
The following fields have had refs support added: - CacheSubnetGroup.SubnetIDs: ec2.Subnet.Status.SubnetID - CacheParameterGroupName: CacheParameterGroup.Spec.CacheParameterGroupName - CacheSubnetGroupName: CacheSubnetGroup.Spec.CacheSubnetGroupName - SecurityGroupIDs: ec2.SecurityGroup.Status.ID Closes aws-controllers-k8s/community#1513 Closes aws-controllers-k8s/community#1860
The following fields have had refs support added: - CacheSubnetGroup.SubnetIDs: ec2.Subnet.Status.SubnetID - ReplicationGroup.CacheParameterGroupName: CacheParameterGroup.Spec.CacheParameterGroupName - ReplicationGroup.CacheSubnetGroupName: CacheSubnetGroup.Spec.CacheSubnetGroupName - ReplicationGroup.SecurityGroupIDs: ec2.SecurityGroup.Status.ID Closes aws-controllers-k8s/community#1513 Closes aws-controllers-k8s/community#1860
The following fields have had refs support added: - CacheSubnetGroup.SubnetIDs: ec2.Subnet.Status.SubnetID - ReplicationGroup.CacheParameterGroupName: CacheParameterGroup.Spec.CacheParameterGroupName - ReplicationGroup.CacheSubnetGroupName: CacheSubnetGroup.Spec.CacheSubnetGroupName - ReplicationGroup.SecurityGroupIDs: ec2.SecurityGroup.Status.ID Closes aws-controllers-k8s/community#1513 Closes aws-controllers-k8s/community#1860
## Issue #, if available: Closes aws-controllers-k8s/community#1513 Closes aws-controllers-k8s/community#1860 ## Description of changes: The following fields have had refs support added: - CacheSubnetGroup.SubnetIDs: ec2.Subnet.Status.SubnetID - ReplicationGroup.CacheParameterGroupName: CacheParameterGroup.Spec.CacheParameterGroupName - ReplicationGroup.CacheSubnetGroupName: CacheSubnetGroup.Spec.CacheSubnetGroupName - ReplicationGroup.SecurityGroupIDs: ec2.SecurityGroup.Status.ID --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Expecting an elasticache-controller release today |
Supported in |
@a-hilaly: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Good day!
I am extensively using Elasticache controller. Unfortunately, right now I need to create SG BEFORE creating the redis instance and getting the precise ID of security group by console means:
I am kindly asking to add
securityGroups
field inec2.services.k8s.aws/v1alpha1
Instance
or likevpcSecurityGroupRefs
inDBInstance
fromrds.services.k8s.aws/v1alpha
. This field will contain references to sg names instead of precise ids.It will allow to remove some unnecessary manual steps.
The text was updated successfully, but these errors were encountered: