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

Ingress Gateways integration with Agentless and Consul Dataplane #1544

Merged
merged 1 commit into from
Sep 28, 2022

Conversation

thisisnotashwin
Copy link
Contributor

Changes proposed in this PR:

  • Register Ingress Gateways using the endpoints controller.
  • Use Consul Dataplane instead of Envoy

How I've tested this PR:

  • Acceptance tests
  • Unit and BATS tests.

How I expect reviewers to test this PR:

  • Code Review

Checklist:

  • Tests added
  • CHANGELOG entry added

    HashiCorp engineers only, community PRs should not add a changelog entry.
    Entries should use present tense (e.g. Add support for...)

@thisisnotashwin thisisnotashwin force-pushed the ashwin/ingress-gateways branch 3 times, most recently from 338d120 to f557b64 Compare September 27, 2022 19:56
Copy link
Contributor

@ishustava ishustava left a comment

Choose a reason for hiding this comment

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

Beautiful!! I had some comments, but won't block assuming they're addressed before merging! Amazing work!

Comment on lines -65 to -71
if !c.secure {
logger.Logf(t, "creating the %s namespace in Consul", testNamespace)
_, _, err := consulClient.Namespaces().Create(&api.Namespace{
Name: testNamespace,
}, nil)
require.NoError(t, err)
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Oh nice! because endpoints controller will create the ns now, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

exactly!!

{{- if (and $root.Values.global.tls.enabled $root.Values.global.tls.enableAutoEncrypt) }}
{{- include "consul.getAutoEncryptClientCA" $root | nindent 8 }}
volumeMounts:
{{- if $root.Values.global.tls.enabled }}
Copy link
Contributor

Choose a reason for hiding this comment

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

this doesn't need to be mounted if external servers with use system roots is set

{{- if $root.Values.global.tls.enabled }}
{{- if not (and $root.Values.externalServers.enabled $root.Values.externalServers.useSystemRoots) }}
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we still need the this if condition

-envoy-ready-bind-address=$POD_IP \
-envoy-ready-bind-port=21000 \
{{- if $root.Values.externalServers.enabled }}
-addresses={{ $root.Values.externalServers.hosts | first }} \
Copy link
Contributor

Choose a reason for hiding this comment

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

we need to quote it so that command like -addresses="exec=..." works

Suggested change
-addresses={{ $root.Values.externalServers.hosts | first }} \
-addresses={{ $root.Values.externalServers.hosts | first | quote }} \

- Use consul-dataplane instead of envoy.
@thisisnotashwin thisisnotashwin merged commit 85d29fd into agentless-base Sep 28, 2022
@thisisnotashwin thisisnotashwin deleted the ashwin/ingress-gateways branch September 28, 2022 03:52
ishustava pushed a commit that referenced this pull request Sep 28, 2022
- Use consul-dataplane instead of envoy.
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.

3 participants