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

ci(deploy-to-kind-cluster): added default env vars #5473

Merged
merged 1 commit into from
Oct 14, 2021

Conversation

gunnar-solo
Copy link
Contributor

@gunnar-solo gunnar-solo commented Oct 14, 2021

Description

  • classify between darwin vs. linux systems when running ci/deploy-to-kind-cluster.sh
  • default KUBE2E_TESTS to eds, rather than nothing

This commit can be used to run ci/deploy-to-kind-cluster.sh on a mac off of a fresh clone with no configuration

Context

One of the more common use-cases for deploy-to-kind-cluster is in local development. Currently, when running the script, some tweaks are needed to have it succeed on a Mac. This is a bit painful, and is time that not every person on a Mac should need to figure out in order to test locally.

Checklist:

  • I included a concise, user-facing changelog (for details, see https://github.com/solo-io/go-utils/tree/master/changelogutils) which references the issue that is resolved.
  • If I updated APIs (our protos) or helm values, I ran make -B install-go-tools generated-code to ensure there will be no code diff
  • I followed guidelines laid out in the Gloo Edge contribution guide
  • I opened a draft PR or added the work in progress label if my PR is not ready for review
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works

@gunnar-solo gunnar-solo force-pushed the ci-script-tweaks branch 2 times, most recently from fad3d67 to 88fe95f Compare October 14, 2021 13:03
\# Description
* classify between `darwin` vs. `linux` systems when running `ci/deploy-to-kind-cluster.sh`
* default `KUBE2E_TESTS` to `eds`, rather than nothing

This commit can be used to run `ci/deploy-to-kind-cluster.sh` on a mac off of a fresh clone with no configuration

\# Context
One of the more common use-cases for `deploy-to-kind-cluster` is in local development.  _Currently_, when running the script, some tweaks are needed to have it _succeed_ on a Mac.  This is a bit painful, and is time that not every person on a Mac should need to figure out in order to test locally.
Copy link
Contributor

@elcasteel elcasteel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, this will definitely make manual testing easier to figure out for future developers.

@gunnar-solo gunnar-solo marked this pull request as ready for review October 14, 2021 15:19
@soloio-bulldozer soloio-bulldozer bot merged commit 1892429 into solo-io:master Oct 14, 2021
@gunnar-solo gunnar-solo deleted the ci-script-tweaks branch October 14, 2021 15:19
ben-taussig-solo pushed a commit that referenced this pull request Oct 14, 2021
* ci(deploy-to-kind-cluster): added default env vars

\# Description
* classify between `darwin` vs. `linux` systems when running `ci/deploy-to-kind-cluster.sh`
* default `KUBE2E_TESTS` to `eds`, rather than nothing

This commit can be used to run `ci/deploy-to-kind-cluster.sh` on a mac off of a fresh clone with no configuration

\# Context
One of the more common use-cases for `deploy-to-kind-cluster` is in local development.  _Currently_, when running the script, some tweaks are needed to have it _succeed_ on a Mac.  This is a bit painful, and is time that not every person on a Mac should need to figure out in order to test locally.
soloio-bulldozer bot pushed a commit that referenced this pull request Oct 15, 2021
* Create General Service Converter
* Update service converter testing
* create settings.DiscoveryOptions.GeneralAnnotationUpstreamConfig setting
* Use widely supported method of iterating over struct fields
* Don't overwrite preexisting config in new converter
* Enable general purpose annotation config processor by default
* Remove no-longer-used general_annotation_upstream_config setting
* Update tests, add new test to confirm that general converter doesn't override Http2 converter
* Merge branch 'master' into general-annotation-config-processor
* Add changelog entry
* Adding changelog file to new location
* Deleting changelog file from old location
* Ensure that general annotation converter is applied first
* Restore check against values set on upstream spec
* Merge branch 'general-annotation-config-processor' of github.com:solo-io/gloo into general-annotation-config-processor
* trigger build
* Revert to init() implementation of serviceConverter intialization
* Refactor GeneralServiceConverter.ConvertService for readability, clarifying comments
* Create translator.MergeUpstreams util
* Testing, clarifying comments around new translator utility
* Generalize struct merge logic
* Remove unnecessary assertion in mergeStructs
* Remove init() approach to creating default service converters, create DefaultServiceConverters method
* Move mergeUpstreams util out of gateway, into general annotation converter
* Allow general purpose converter to overwrite config from other converters
* Define init function in service_converter_interface.go
* Swap position of src and dst arguments in mergeUpstreams
* Handle output of mergeUpstreams
* Don't return upstream from mergeUpstreams
* Dont return anything from mergeUpstream
* trigger build
* Remove isEmptyValue from general_annotation_converter.go
* Add user guide for general annotation config
* resolve outstanding issues with general annotation converter
* ci(deploy-to-kind-cluster): added default env vars (#5473)

* ci(deploy-to-kind-cluster): added default env vars

\# Description
* classify between `darwin` vs. `linux` systems when running `ci/deploy-to-kind-cluster.sh`
* default `KUBE2E_TESTS` to `eds`, rather than nothing

This commit can be used to run `ci/deploy-to-kind-cluster.sh` on a mac off of a fresh clone with no configuration

\# Context
One of the more common use-cases for `deploy-to-kind-cluster` is in local development.  _Currently_, when running the script, some tweaks are needed to have it _succeed_ on a Mac.  This is a bit painful, and is time that not every person on a Mac should need to figure out in order to test locally.
* Update docs/content/guides/traffic_management/destination_types/discovered_upstream/discovered-upstream-configuration.md

Co-authored-by: Art <artberger@users.noreply.github.com>

Update docs/content/guides/traffic_management/destination_types/discovered_upstream/discovered-upstream-configuration.md

Co-authored-by: Art <artberger@users.noreply.github.com>

Update docs/content/guides/traffic_management/destination_types/discovered_upstream/discovered-upstream-configuration.md

Co-authored-by: Art <artberger@users.noreply.github.com>

Update docs/content/guides/traffic_management/destination_types/discovered_upstream/discovered-upstream-configuration.md

Co-authored-by: Art <artberger@users.noreply.github.com>

Update docs/content/guides/traffic_management/destination_types/discovered_upstream/discovered-upstream-configuration.md

Co-authored-by: Art <artberger@users.noreply.github.com>

Update docs/content/guides/traffic_management/destination_types/discovered_upstream/discovered-upstream-configuration.md

Co-authored-by: Art <artberger@users.noreply.github.com>
* Merge branch 'master' into general-annotation-config-processor
* Resolve failing tests
* Merge branch 'general-annotation-config-processor' of github.com:solo-io/gloo into general-annotation-config-processor
* Return Spec to function-level scope, clarify fields that cannot be written to
* Update general config serviceconverter to no longer require top-level spec field in incoming config
* Update docs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants