update docs: updating kops

[nothinux]

No description provided.

[k8s-ci-robot]

Hi @nothinux. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[johngmyers]

The two merge commits appear to be superfluous. Could they be removed?
/ok-to-test

[nothinux]

@johngmyers i don't know how to remove the commits, can you tell me how to do that ?

[johngmyers]

git rebase upstream/master followed by a force-push would probably do it.

[nothinux]

thanks for your help @johngmyers , the commit was removed

[johngmyers]

/retest
/lgtm

[rifelpet]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nothinux, rifelpet

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:

• OWNERS [rifelpet]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[johngmyers]

/area documentation

[johngmyers]

/retest

[johngmyers]

/retest

[rifelpet]

/test pull-kops-e2e-kubernetes-aws