Skip to content

Conversation

Jan-M
Copy link
Member

@Jan-M Jan-M commented Dec 16, 2020

Enable AWS gp3 support in manifest, allowing configuration of IOPS and Throughput and Size.

Potentially includes full support for EBS volume types with that. Thus ìo2.

@zalando-robot
Copy link

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 library and use a recommended version as listed in the documentation.

@zalando-robot
Copy link

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 library and use a recommended version as listed in the documentation.

}

if c.OpConfig.StorageResizeMode == "mixed" {
// mixed op uses AWS API to adjust size,throughput,iops and calls pvc chance for file system resize
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. This phrase is documentation rather than comment.
  2. I assume "chance" should really be change

var err error

targetValue := c.Spec.Volume
newSize, err := resource.ParseQuantity(targetValue.Size)
Copy link
Member

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.

@zalando-robot
Copy link

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 library and use a recommended version as listed in the documentation.

@zalando-robot
Copy link

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 library and use a recommended version as listed in the documentation.

@zalando-robot
Copy link

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 library and use a recommended version as listed in the documentation.

@zalando-robot
Copy link

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 library and use a recommended version as listed in the documentation.

@Jan-M Jan-M changed the title Initial commit for full AWS gp3 support. Full AWS gp3 support for iops and througput config. Jan 20, 2021
@zalando-robot
Copy link

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 library and use a recommended version as listed in the documentation.

@zalando-robot
Copy link

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 library and use a recommended version as listed in the documentation.

* **subPath**
Subpath to use when mounting volume into Spilo container. Optional.

* **iops**
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and the defaults for iopsand throughput are ... ?

return nil
}

func (c *Cluster) syncUnderlyingEBSVolume() error {
Copy link
Member

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

@sdudoladov
Copy link
Member

👍

2 similar comments
@Jan-M
Copy link
Member Author

Jan-M commented Jan 25, 2021

👍

@Jan-M
Copy link
Member Author

Jan-M commented Jan 25, 2021

👍

@Jan-M Jan-M merged commit 4a88f00 into master Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants