By default the controller is configured to skip resolving
for the following registries:
- ko.local
- dev.local
This should address issue #1093
Co-authored-by: Sukhil Suresh <ssuresh@pivotal.io>
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
(https://github.com/kubernetes/minikube/pull/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 https://github.com/kubernetes/minikube/issues/384) - another
step along the road to #608.
Failed with group name `cluster`:
```
± |master ✓| → gcloud container cluster get-credentials ssuresh-knative-dev
ERROR: (gcloud.container) Invalid choice: 'cluster'. Did you mean 'clusters'?
Usage: gcloud container [optional flags] <group | command>
group may be builds | clusters | images | node-pools | operations
command may be get-server-config
For detailed information on this command and its flags, run:
gcloud container --help
```
Works with group name `clusters`:
```
± |master ✓| → gcloud container clusters get-credentials ssuresh-knative-dev
Fetching cluster endpoint and auth data.
kubeconfig entry generated for ssuresh-knative-dev.
```
* Rename most ela-* things
Left `ela-prow` since that is an external dependency that might break.
* Fix filenames
* Revert some e2e test changes
* attempt to fight the Walk function
* Address feedback
* Rearrange yaml order
Attempt to reflect the important-looking order from bazel's build rules.
See: a15e38795b/config/BUILD.bazel (L121-L138)
* elafros/elafros -> knative/service
* replace elafros with knative
* changed ela package to serving
* change elafros/build to knative/build and newer version
* things are running mostly
* address build / test failures
* address integration test failures
* repo has not chnaged
* Remove SecurityContextDeny from minikube instructions
Fixes#507
* Updated docs to work with minikube v0.26.0 and later
Fixes#801
- use explicit bootstrapper arg and
- also added a macOS specific startup command for easier cut-and-paste.
* Fix typo
* Switch to use `hyperkit` vm-driver instead of `xhyve` on macOS
The certificate controller is required to configure the istio sidecar
injector webhook, but Minikube doesn't give it the paths to the CA certs
by default, so it can't start.
These paths are local to the VM, not the host machine, so they are the
same for all users.
Use 4 CPU nodes in setup instructions
The conformance tests have been failing and in @josephburnett 's investigation he found that it was the autoscaler changes made the tests CPU starved, and so we need beefier machines to be able to run the tests (i.e. to run elafros).
Follow up work still todo: documenting minimum system requirements.
* Remove extra _ in markdown file.
* Fix flag for running conformance tests with bazel.
* Fix conformance tests.
Commit #300 updated Route.Spec.Traffic.{Revision,Configuration} to end with Name.
1. Change - unordered list to use *
2. Change ordered lists to use lazy numbering (write 1 inline instead of
2-9)
3. Fix line lengths
4. Fix indentation on shell code sample
* Add docs for using minikube with GCR
* Add example showing creation of image pull secret
* Clarify that secrets are per-namespace
* GCR has repos, not instances
* create secrets for build-controller too
* Mention default service account and more docs
* Add env var for GCR domain
* Link to kubernetes cluster doc
* Clean up general setup steps and minikube docs
* Remove comments and correct multiline command
Comments break copy-paste
* Add documentation for creating a K8S cluster
The GKE instructions have been verified to work, but Minikube is a WIP.
* fix some formatting
* indent code block correctly
* Specify that this is Elafros-specific
jonjohnsonjr
Jason Hall
Sukhil Suresh
Christie Wilson
Thomas Risberg
Nghia Tran
Evan Anderson
Matt Moore
Ville Aikas
akyyy
Grant Rodgers
Joseph Burnett
Adriano Cunha
Drew Inglis