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

Automate building developer environment #2417

Merged
merged 1 commit into from
Apr 24, 2018

Conversation

zrdaley
Copy link
Contributor

@zrdaley zrdaley commented Apr 24, 2018

What this PR does / why we need it:

Setting up the development environment is quite time consuming and somewhat confusing. This script creates a quick command that will allow MacOS developers to set up their quickly by automating the following tasks:

1. Stop and uninstall minikube
2. Install minikube version 0.25.0
3. Start minikube
4. Dep ensure to get vendor/ dependencies
5. Build the local ingress controller container
6. Install kubectl
7. Deploy the controller & update the image

Which issue this PR fixes: N/A

Special notes for your reviewer:

Minikube versions > 0.25.0 enable RBAC on the cluster. This will cause the e2e-tests to fail. Therefore a suitable development environment requires version 0.25.0 or less.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Apr 24, 2018
@aledbf
Copy link
Member

aledbf commented Apr 24, 2018

Minikube versions > 0.25.0 enable RBAC on the cluster. This will cause the e2e-tests to fail. Therefore a suitable development environment requires version 0.25.0 or less.

I am going to simplify the manifests and enable RBAC by default so this is not going to be an issue.

$ make dev-env
```

**IMPORTANT**: This will uninstall minikube from your machine and reinstall version 0.25.0.
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we absolutely need to enforce this? RBAC can happily coexist with the AlwaysAllow authorization mode and be enabled for auditing only. I believe most developers want to keep their local environment up to date.

Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe that (quite unknown) feature would be less destructive? kubernetes/minikube#2371

Copy link
Member

Choose a reason for hiding this comment

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

@antoineco profiles do not work with --vm-driver=kvm2 :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's only an issue because of the e2e-tests failing. This won't be an issue once @aledbf makes the updates mentioned above. I can remove this part of the script and then deploy with RBAC instead.

@codecov-io
Copy link

codecov-io commented Apr 24, 2018

Codecov Report

Merging #2417 into master will increase coverage by 0.13%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2417      +/-   ##
==========================================
+ Coverage   40.91%   41.05%   +0.13%     
==========================================
  Files          74       74              
  Lines        5252     5252              
==========================================
+ Hits         2149     2156       +7     
+ Misses       2809     2803       -6     
+ Partials      294      293       -1
Impacted Files Coverage Δ
cmd/nginx/main.go 26.2% <0%> (+4.82%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c0cc3e5...58f5eb4. Read the comment docs.

@antoineco
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 24, 2018
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 24, 2018
@aledbf
Copy link
Member

aledbf commented Apr 24, 2018

@zrdaley please squash the commits

@aledbf
Copy link
Member

aledbf commented Apr 24, 2018

/approve

@aledbf
Copy link
Member

aledbf commented Apr 24, 2018

/lgtm

@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm "Looks good to me", indicates that a PR is ready to be merged. labels Apr 24, 2018
@aledbf
Copy link
Member

aledbf commented Apr 24, 2018

@zrdaley thanks!

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aledbf, antoineco, zrdaley

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit 57c10f9 into kubernetes:master Apr 24, 2018
@zrdaley zrdaley deleted the dev-up branch April 24, 2018 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants