-
Notifications
You must be signed in to change notification settings - Fork 1k
Full AWS gp3 support for iops and througput config. #1261
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
Conversation
Docker image "registry-write.opensource.zalan.do/acid/postgres-operator-ui-test:v1.5.0-106-g0760b94-pr-1261-6" is not based on an approved base image. Currently, this will have no impact on your deployments, but builds using non-allowed images will be blocked from deployment from February 1st 2021. To create a compliant Docker image of your application, you must reference an allowed Docker image as its base image in your Dockerfile. This base image must come from the Open Source Registry namespace |
Docker image "registry-write.opensource.zalan.do/acid/postgres-operator-ui-test:v1.5.0-108-g89886a9-pr-1261-8" is not based on an approved base image. Currently, this will have no impact on your deployments, but builds using non-allowed images will be blocked from deployment from February 1st 2021. To create a compliant Docker image of your application, you must reference an allowed Docker image as its base image in your Dockerfile. This base image must come from the Open Source Registry namespace |
pkg/cluster/volumes.go
Outdated
} | ||
|
||
if c.OpConfig.StorageResizeMode == "mixed" { | ||
// mixed op uses AWS API to adjust size,throughput,iops and calls pvc chance for file system resize |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- This phrase is documentation rather than comment.
- I assume "chance" should really be change
var err error | ||
|
||
targetValue := c.Spec.Volume | ||
newSize, err := resource.ParseQuantity(targetValue.Size) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please do not ignore errors.
Docker image "registry-write.opensource.zalan.do/acid/postgres-operator-test:v1.5.0-110-g259a5d6-dirty-pr-1261-10" is not based on an approved base image. Currently, this will have no impact on your deployments, but builds using non-allowed images will be blocked from deployment from March 1st 2021. To create a compliant Docker image of your application, you must reference an allowed Docker image as its base image in your Dockerfile. This base image must come from the Open Source Registry namespace |
Docker image "registry-write.opensource.zalan.do/acid/postgres-operator-ui-test:v1.5.0-110-g5af81cf-pr-1261-10" is not based on an approved base image. Currently, this will have no impact on your deployments, but builds using non-allowed images will be blocked from deployment from March 1st 2021. To create a compliant Docker image of your application, you must reference an allowed Docker image as its base image in your Dockerfile. This base image must come from the Open Source Registry namespace |
Docker image "registry-write.opensource.zalan.do/acid/postgres-operator-test:v1.5.0-111-ge3a6b32-dirty-pr-1261-11" is not based on an approved base image. Currently, this will have no impact on your deployments, but builds using non-allowed images will be blocked from deployment from March 1st 2021. To create a compliant Docker image of your application, you must reference an allowed Docker image as its base image in your Dockerfile. This base image must come from the Open Source Registry namespace |
Docker image "registry-write.opensource.zalan.do/acid/postgres-operator-ui-test:v1.5.0-111-g2cc71bf-pr-1261-11" is not based on an approved base image. Currently, this will have no impact on your deployments, but builds using non-allowed images will be blocked from deployment from March 1st 2021. To create a compliant Docker image of your application, you must reference an allowed Docker image as its base image in your Dockerfile. This base image must come from the Open Source Registry namespace |
Docker image "registry-write.opensource.zalan.do/acid/postgres-operator-test:v1.5.0-114-g3063d73-dirty-pr-1261-14" is not based on an approved base image. Currently, this will have no impact on your deployments, but builds using non-allowed images will be blocked from deployment from March 1st 2021. To create a compliant Docker image of your application, you must reference an allowed Docker image as its base image in your Dockerfile. This base image must come from the Open Source Registry namespace |
Docker image "registry-write.opensource.zalan.do/acid/postgres-operator-ui-test:v1.5.0-114-g757f284-pr-1261-14" is not based on an approved base image. Currently, this will have no impact on your deployments, but builds using non-allowed images will be blocked from deployment from March 1st 2021. To create a compliant Docker image of your application, you must reference an allowed Docker image as its base image in your Dockerfile. This base image must come from the Open Source Registry namespace |
81d867b
to
4cee9b8
Compare
@@ -356,6 +356,14 @@ properties of the persistent storage that stores Postgres data. | |||
* **subPath** | |||
Subpath to use when mounting volume into Spilo container. Optional. | |||
|
|||
* **iops** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and the defaults for iops
and throughput
are ... ?
return nil | ||
} | ||
|
||
func (c *Cluster) syncUnderlyingEBSVolume() error { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
imo Underlying
is self-evident. Omitting the word from the method name would make it more readable
👍 |
2 similar comments
👍 |
👍 |
Enable AWS gp3 support in manifest, allowing configuration of
IOPS
andThroughput
andSize
.Potentially includes full support for EBS volume types with that. Thus
ìo2
.