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

Add real local target #928

Merged
merged 4 commits into from
Apr 30, 2024
Merged

Add real local target #928

merged 4 commits into from
Apr 30, 2024

Conversation

dbadura
Copy link
Contributor

@dbadura dbadura commented Apr 25, 2024

Description

Changes proposed in this pull request:

  • add target which build operator, serverless and runtimes locally and install it

Related issue(s)
#826

@kyma-bot kyma-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 25, 2024
@kyma-bot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@dbadura dbadura marked this pull request as ready for review April 25, 2024 10:25
@kyma-bot kyma-bot added cla: yes Indicates the PR's author has signed the CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Apr 25, 2024

##@ 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
Copy link
Contributor Author

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
Copy link
Contributor

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

pPrecel
pPrecel previously approved these changes Apr 29, 2024
echo "==== Local Changes ===="
yq '.global.images' ${VALUES_FILE}
yq '.global.images' "${VALUES_FILE}"
yq '.global.containerRegistry' "${VALUES_FILE}"
Copy link
Contributor

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

@kyma-bot kyma-bot added the lgtm Looks good to me! label Apr 29, 2024
@halamix2
Copy link
Member

/retest pre-serverless-runtimes-nodejs-v18-build
/retest pre-serverless-runtimes-nodejs-v20-build
/retest pre-serverless-runtimes-python312-build
/retest pre-serverless-runtimes-python39-build

@kyma-bot
Copy link
Contributor

@halamix2: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test pre-serverless-controller-build
  • /test pre-serverless-jobinit-build
  • /test pre-serverless-operator-build
  • /test pre-serverless-runtimes-java17-jvm-alpha-build
  • /test pre-serverless-runtimes-nodejs-v18-build
  • /test pre-serverless-runtimes-python312-build
  • /test pre-serverless-runtimes-python39-build
  • /test pre-serverless-webhook-build

The following commands are available to trigger optional jobs:

  • /test pre-gitserver-build
  • /test pre-serverless-runtimes-nodejs-v20-build

Use /test all to run the following jobs that were automatically triggered:

  • pre-serverless-controller-build
  • pre-serverless-jobinit-build
  • pre-serverless-operator-build
  • pre-serverless-runtimes-java17-jvm-alpha-build
  • pre-serverless-runtimes-nodejs-v18-build
  • pre-serverless-runtimes-nodejs-v20-build
  • pre-serverless-runtimes-python312-build
  • pre-serverless-runtimes-python39-build
  • pre-serverless-webhook-build

In response to this:

/retest pre-serverless-runtimes-nodejs-v18-build
/retest pre-serverless-runtimes-nodejs-v20-build
/retest pre-serverless-runtimes-python312-build
/retest pre-serverless-runtimes-python39-build

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.

@halamix2
Copy link
Member

/test pre-serverless-runtimes-nodejs-v18-build
/test pre-serverless-runtimes-nodejs-v20-build
/test pre-serverless-runtimes-python312-build
/test pre-serverless-runtimes-python39-build

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@kyma-bot kyma-bot removed the lgtm Looks good to me! label Apr 29, 2024
@kyma-bot kyma-bot added the lgtm Looks good to me! label Apr 29, 2024
@kyma-bot kyma-bot merged commit 182cbbe into kyma-project:main Apr 30, 2024
24 checks passed
@dbadura dbadura deleted the local-target branch May 6, 2024 06:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Indicates the PR's author has signed the CLA. lgtm Looks good to me! 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.

5 participants