Skip to content
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

will support aws cn-north-1 and cn-northwest-1 regions? #1354

Closed
tj13 opened this issue Mar 4, 2019 · 7 comments
Closed

will support aws cn-north-1 and cn-northwest-1 regions? #1354

tj13 opened this issue Mar 4, 2019 · 7 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. platform/aws

Comments

@tj13
Copy link

tj13 commented Mar 4, 2019

will openshift 4.0 support install in aws cn-north-1 and cn-northwest-1 regions?

@wking
Copy link
Member

wking commented Mar 4, 2019

At the moment, we only support regions where the RHCOS team publishes AMIs. The encrypted-copy approach begun in #1296 will allow for clusters in any region (once we get machine-API support for encrypted compute nodes, so probably a bit out yet). In the meantime, you can copy your own AMIs into your target region and use those, although that might make automatic RHCOS upgrades tricky (or maybe the OSTree pivots would be fine, I dunno).

@tj13
Copy link
Author

tj13 commented Mar 6, 2019

how about custom installation on centos 7 which hosted by EC2?

@wking
Copy link
Member

wking commented Jul 29, 2019

Cross-linking rhbz#1734136.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 20, 2020
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 21, 2020
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci-robot
Copy link
Contributor

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. platform/aws
Projects
None yet
Development

No branches or pull requests

4 participants