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

Initial work to opensource guardian #9849

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Brian-McM
Copy link
Contributor

Description

Related issues/PRs

Todos

  • Tests
  • Documentation
  • Release note

Release Note

TBD

Reminder for the reviewer

Make sure that this PR has the correct labels and milestone set.

Every PR needs one docs-* label.

  • docs-pr-required: This change requires a change to the documentation that has not been completed yet.
  • docs-completed: This change has all necessary documentation completed.
  • docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

  • release-note-required: This PR has user-facing changes. Most PRs should have this label.
  • release-note-not-required: This PR has no user-facing changes.

Other optional labels:

  • cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
  • needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

@marvin-tigera marvin-tigera added this to the Calico v3.30.0 milestone Feb 14, 2025
@marvin-tigera marvin-tigera added release-note-required Change has user-facing impact (no matter how small) docs-pr-required Change is not yet documented labels Feb 14, 2025
@Brian-McM Brian-McM force-pushed the bm-add-guardian-to-oss branch 6 times, most recently from a84cc49 to 8581bb4 Compare February 18, 2025 17:50
This commit adds guardian, a component that can connect to calico cloud. This facilitates open source clusters connecting to calico free tier.
@Brian-McM Brian-McM force-pushed the bm-add-guardian-to-oss branch from 8581bb4 to 09d1626 Compare February 18, 2025 19:19
tlsCfg := tls.NewTLSConfig()

if tgt.AllowInsecureTLS {
tlsCfg.InsecureSkipVerify = true
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we drop this setting ?

ClientCertPath string `json:"clientCertPath"`
ClientKeyPath string `json:"clientKeyPath"`

Unauthenticated bool `json:"unauthenticated,omitempty"`
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this removed?

ListenAndServeManagementCluster(ctx context.Context) error
}

// Client is the voltron client. It is used by Guardian to establish a secure tunnel connection to the Voltron server and
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 this is called server now and it is not public.

http: new(http.Server),

tunnelAddr: addr,
tunnelServerName: strings.Split(addr, ":")[0],
Copy link
Contributor

Choose a reason for hiding this comment

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

What if we have an IPV6 address ?


var dialer tunnel.SessionDialer
if srv.tunnelCert == nil {
log.Warnf("No tunnel creds, using unsecured tunnel")
Copy link
Contributor

Choose a reason for hiding this comment

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

We should probably drop support for unsecure tunnel

)

const (
tunnelNetwork = "voltron-tunnel"
Copy link
Contributor

Choose a reason for hiding this comment

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

I wonder if there is any benefits to configure this at start up instead of hard-coding it. In case we want to change it, it would be better to not hard-coded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-pr-required Change is not yet documented release-note-required Change has user-facing impact (no matter how small)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants