-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 minikube docs post rename #1332
Update minikube docs post rename #1332
Conversation
1dc6984
to
c9fcbc0
Compare
kubectl apply -f ./third_party/istio-0.8.0/istio.yaml | ||
``` | ||
|
||
Then label namespaces with `istio-injection=enabled`: | ||
Optionally label namespaces with `istio-injection=enabled`: |
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.
@tcnghia this IS optional right? I don't enable injection for any of my non-default namespaces, and it's not enabled for the e2e namespaces in the automated tests, and things still work, but I'm not sure if that's intentional
I saw some issues with the image pull secrets following the sequence in the docs. worked better when first creating the knative-serving namespace and the service account using:
and then adding the imagePullSecret to the "controller" service account before doing the full knative-serving deploy. |
kk, I'll update the docs, thanks @trisberg ! |
ee7e5f1
to
01805ed
Compare
1. Deploy the rest of Knative: | ||
```bash | ||
ko apply -f config/ | ||
``` |
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.
@trisberg The instructions are a bit rough, let me know if you can think of a clearer way of explaining this, or if I've missed anything!
(I also found this a more reliable sequence of actions than recreating the controllers, etc., after deploying!)
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 hard because these steps depend on the GCR instructions below. I think it is fine the way it you have it now
ko apply -f config/ | ||
``` | ||
|
||
1. [Enable log and metric collection](../DEVELOPMENT.md#enable-log-and-metric-collection) |
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.
we should mention that 8GB might not be enough for the elasticsearch components - I've found that 12GB works better
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.
Added!
01805ed
to
f366308
Compare
DEVELOPMENT.md
Outdated
|
||
### Deploy Istio | ||
1. [Make your user a cluster admin](#setup-cluster-admin) |
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.
one more thing, don't think you need this for minikube, I always run without this step
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.
great, removed!
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.
... okay it wasn't removed but NOW it will be :D
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.
actually - since this is in DEVELOPMENT.md
it covers both Minikube and GKE, so we should leave it in and maybe add a comment that it can be skipped for Minikube
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.
lol thanks for catching this, just re-fixed it XD
f366308
to
2036c47
Compare
cluster, e.g. [GCR](#minikube-with-gcr), you will need to deploy Knative | ||
itself a bit differently: | ||
|
||
1. [Deploy istio](../DEVELOPMENT.md#deploy-istio) |
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.
We should add: For Minikube replace LoadBalancer
with NodePort
using:
sed 's/LoadBalancer/NodePort/' third_party/istio-0.8.0/istio.yaml | \
kubectl apply -f -
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.
i will add that! that might actually solve most of #609 I have a feeling - I want to follow up and see if we can make this process a bit more automatic for the minikube case as well.
for prefix in ela build; do | ||
kubectl create secret docker-registry "gcr" \ | ||
export [email protected] | ||
for prefix in knative-serving build; do |
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.
the knative-serving
namespace no longer has a system
suffix, I suspect that this will need to be adjusted again if the build namespace changes
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.
oh yeah i missed that, thanks @trisberg !!
/approve I'm going to let @trisberg do the /lgtm, assuming that I understand how Prow works. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bobcatfish, evankanderson 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 |
/assign @trisberg |
2036c47
to
fb63486
Compare
fb63486
to
404b15c
Compare
|
||
(Then optionally [enable istio injection](../DEVELOPMENT.md#deploy-istio).) | ||
|
||
1. [Deploy build](../DEVELOPMENT.md#deploy-build) |
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.
i think at this point i should duplicate this line in this doc, since the rest of the steps are explicit
The docs for setting up minikube were using the namespaces and resource names from elafros instead of knative. The naming changed slightly, e.g. a knative controller is now called `controller` instead of `knative-serving-controller`, so one of the loops had to be broken into 2 statements. Added steps about redeploying pods after setting up GCR secrets b/c there is a chicken and egg problem where the namespaces must exist before you can setup the secrets, but the secrets must exist before the images can be pulled. The PR that enabled `MutatingAdmissionWebhook` by default (kubernetes/minikube#2547) was merged, but the latest minikube (0.28.0) still did not enable this option by default b/c providing any arugments overrides all of the defaults, so we must still set it explicitly. Made it clear in the setting up knative serving docs that the cluster admin binding is required, not just for istio. Use a `NodePort` instead of a `LoadBalancer` (see kubernetes/minikube#384) - another step along the road to #608.
404b15c
to
b4ea5c6
Compare
/lgtm |
The docs for setting up minikube were using the namespaces and
resource names from elafros instead of knative. The naming changed
slightly, e.g. a knative controller is now called
controller
instead of
knative-serving-controller
, so one of the loops hadto be broken into 2 statements.
Added steps about redeploying pods after setting up GCR
secrets b/c there is a chicken and egg problem where the namespaces
must exist before you can setup the secrets, but the secrets must
exist before the images can be pulled.
The PR that enabled
MutatingAdmissionWebhook
by default(kubernetes/minikube#2547) was merged, but
the latest minikube (0.28.0) still did not enable this option
by default b/c providing any arugments overrides all of the defaults,
so we must still set it explicitly.
Made it clear in the setting up knative serving docs that the cluster
admin binding is required, not just for istio.
Proposed Changes