-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add real local target #928
Conversation
Skipping CI for Draft Pull Request. |
|
||
##@ K3D | ||
|
||
.PHONY: create-k3d | ||
create-k3d: kyma ## Create k3d with kyma CRDs. | ||
${KYMA} provision k3d --registry-port ${REGISTRY_PORT} --name ${CLUSTER_NAME} --ci -p 6080:8080@loadbalancer -p 6433:8433@loadbalancer | ||
create-k3d: delete-k3d ## Delete old k3d registry and cluster. Create preconfigured k3d with registry |
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 kyma cli used to delete old k3d and registry, As I used plain k3d
cli I added delete-k3d
as dependency to create-k3d
target
README.md
Outdated
``` | ||
|
||
You have to add `127.0.0.1 k3d-kyma-registry.locahost` to your `etc/hosts`. | ||
More details: https://k3d.io/v5.3.0/usage/registries/#preface-referencing-local-registries |
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 would suggest trying to push built image to the localhost:5000
registry and then pull it from the k3d-kyma-registry.localhost:5000
(from inside the cluster). I think in this case there is no need to push image to the k3d-kyma-registry.localhost:5000
and path hosts
echo "==== Local Changes ====" | ||
yq '.global.images' ${VALUES_FILE} | ||
yq '.global.images' "${VALUES_FILE}" | ||
yq '.global.containerRegistry' "${VALUES_FILE}" |
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 would suggest to install yq
in bin
if it doesn't exist. We don't need to generate another requirement for every developer/user
/retest pre-serverless-runtimes-nodejs-v18-build |
@halamix2: The
The following commands are available to trigger optional jobs:
Use
In response to this:
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. |
/test pre-serverless-runtimes-nodejs-v18-build |
Co-authored-by: Natalia Sitko <[email protected]>
Description
Changes proposed in this pull request:
Related issue(s)
#826