-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
update link so that user can easily jump to CAIP after deployment #2377
Conversation
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.
/lgtm
|
||
## Hosted Kubeflow Pipelines Console | ||
|
||
Please go to [Hosted Kubeflow Pipelines Console](https://console.cloud.google.com/ai-platform/pipelines/clusters). |
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.
personal opinion, shall we add a little more description telling what this page does? Larger space in the screen also means it gets user attention easier.
info: | ||
- name: Application Namespace | ||
value: {{ .Release.Namespace }} | ||
- name: Console | ||
value: 'https://console.cloud.google.com/ai-platform/pipelines/clusters' |
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.
it's pure text, not a link. Link is not supported for now.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rmgogogo The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
) Until now KServe was using the global HTTP endpoint for S3 by default unless the user explicitly provides it with the corresponding annotation. If one wants to use IAM roles for service accounts instead of Secrets with HMAC credentials, storage-initializer will fail in case: * the bucket is configured with SSE * if the bucket allows HTTPS requests only * of an airgapped environment Specifically, if the bucket is configured with SSE it fails with: botocore.exceptions.ClientError: An error occurred (InvalidArgument) when calling the GetObject operation: Requests specifying Server Side Encryption with AWS KMS managed keys must be made over a secure connection. If the bucket policy allows HTTPS requests only it fails with: botocore.exceptions.ClientError: An error occurred (AccessDenied) when calling the ListObjects operation: Access Denied In case of an airgapped environment, S3 is only available via the regional VPC endpoint so requests to the global endpoint will hang. Handle the above cases by letting boto3 decide the S3 endpoint based on the environment. In case of IRSA, AWS will set AWS_REGION and AWS_DEFAULT_REGION and as such boto3 will use the regional endpoint. boto3 will use HTTPS by default which is inline with the default value of s3-usehttps annotation. Finally, if the bucket is in different region boto3 will be automatically redirected there. This change should not break existing deployments that don't use IRSA but don't set s3-endpoint either; boto3 will default using the global HTTPS endpoint, https://s3.amazonaws.com. Handle also the case where endpoint_url is unset or empty, where boto3 fails with: ValueError: Invalid endpoint: With this commit, one can use service accounts with the `eks.amazonaws.com/role-arn` and `eks.amazonaws.com/sts-regional-endpoints` annotations directly without the need of an attached secret. Refs kubeflow#2003 Refs kubeflow#2113 Signed-off-by: Dimitris Aragiorgis <dimara@arrikto.com> Signed-off-by: Dimitris Aragiorgis <dimara@arrikto.com>
This change is