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

Add Ascend.io to USERS.md #24775

Merged
merged 1 commit into from
Apr 11, 2023
Merged

Add Ascend.io to USERS.md #24775

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 6 additions & 0 deletions USERS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,12 @@ Users (Alphabetically)
L: https://cloud.arangodb.com
Q: @ewoutp @Robert-Stam

* N: Ascend.io
D: Ascend.io is using Cilium as a consistent CNI for our Data Automation Platform on GKE, EKS, and AKS.
U: Transparent Encryption, Overlay Networking, Cluster Mesh, Egress Gateway, Network Policy, Hubble
Copy link
Member

Choose a reason for hiding this comment

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

I'm guessing Transparent Encryption is with WireGuard, 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.

We actually initially implemented with IPSec, but it looks like we're likely to transition to wireguard soon since the clouds all bumped their kernels to 5.10 with k8s 1.24 (partially because of incompatibility between ip-sec and some other features, I forget if it was cluster mesh or egress gateway that was the forcing function)

Copy link
Member

Choose a reason for hiding this comment

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

Thanks for the answer!

partially because of incompatibility between ip-sec and some other features, I forget if it was cluster mesh or egress gateway that was the forcing function

Probably egress gateway because IPsec is incompatible with KPR and egress gateway requires KPR. We're working on removing that limitation for IPsec.

L: https://www.ascend.io/
Q: @Joe Stevens

* N: Ayedo
D: Ayedo builds and operates cloud-native container platforms based on Kubernetes
U: Hubble for Visibility, Cilium as Mesh between Services
Expand Down