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.

Sign up for GitHub

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

Jump to bottom

Setup basic integration test on GCP #65

Closed
linki opened this issue Mar 7, 2017 · 5 comments
Closed

Setup basic integration test on GCP #65

linki opened this issue Mar 7, 2017 · 5 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Milestone
v1.0

Comments

@linki
Copy link
Member

linki commented Mar 7, 2017

I'll try to setup a basic integration test for Services on Google Cloud Platform.

This will run in its own Google project, gets a valid DNS name, spins up a cluster running external-dns inside. At some point we may be able to run it wherever CNCF runs the Kubernetes integration tests?
@linki linki mentioned this issue Mar 7, 2017
Closed
@linki linki modified the milestones: v1.0, v0.4 Apr 3, 2017
@linki linki added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Apr 10, 2017
@linki
Copy link
Member Author

linki commented Apr 10, 2017

There's a basic bash script going through the whole flow in #63

@linki linki modified the milestones: post-v0.3-stabilization, v1.0 Jun 12, 2017
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 21, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 21, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

lou-lan pushed a commit to lou-lan/external-dns that referenced this issue May 11, 2022
@ahmetb
pkg/env: allow base path override with KREW_ROOT (kubernetes-sigs#65)
8a8e2b3 
Introduces a KREW_ROOT environment variable to allow overriding
the krew base installation directory (defaults to $HOME/.krew).

Updated installation instructions to add default path to bashrc/zshrc.

Fixes kubernetes-sigs#58.

Signed-off-by: Ahmet Alp Balkan <ahmetb@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
v1.0
Development

No branches or pull requests
3 participants
@linki @k8s-ci-robot @fejta-bot