Add RHEL 8 support to kops (GA May 7, 2019)

[neoakris]

1. Describe IN DETAIL the feature/behavior/change you would like to see.
RHEL8 achieved GA May 7, 2019
https://developers.redhat.com/blog/2019/05/07/red-hat-enterprise-linux-8-now-generally-available/
I'd like to see kops upstream add support for it.

2. Feel free to provide a design supporting your feature request.
@cassandracomar added support on https://github.com/VibrentHealth/kops/tree/rhel8
I was able to build kops off that branch, use an overridden KOPS_BASE_URL env var + custom binary + custom RHEL8 AMI (se linux disabled) in instancegroups.yaml to successfully get a RHEL8 cluster provisioned with kops.

I'd like to see the change get merged into release-1.13 so we wouldn't need to use custom kops in the future when 1.13 gets released.

---

Update:
No mention of it in the release notes of kops 1.13.0 (hopefully a patch version will include it.)
It has been cherry picked into kops 1.14.0, so maybe it'll be in 1.14.0-alpha.4 or higher

[neoakris]

PR #7287
^ has been merged
Don't yet see it in a release though

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.

[rifelpet]

/reopen
/remove-lifecycle rotten

@hakman has been working on adding support. We now have end-to-end tests for RHEL 8 as well

https://testgrid.k8s.io/sig-cluster-lifecycle-kops#kops-aws-rhel-8

[k8s-ci-robot]

@rifelpet: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

@hakman has been working on adding support. We now have end-to-end tests for RHEL 8 as well

https://testgrid.k8s.io/sig-cluster-lifecycle-kops#kops-aws-rhel-8

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.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[hakman]

This was fixed by #8164 and will be available in Kops 1.18.
RHEL uses iptables NFT only, which is only supported in Kubernetes 1.17+.

Backporting will not be possible due to dependencies on other fixes.

[hakman]

/close

[k8s-ci-robot]

@hakman: Closing this issue.

In response to this:

/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.