Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C Cluster applications
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 36
    • Issues 36
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 3
    • Merge requests 3
  • Requirements
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • cluster-integration
  • Cluster applications
  • Merge requests
  • !22

Merged
Created Dec 11, 2019 by Arthur Evstifeev@aevstifeevContributor

Add Cilium cluster application

  • Overview 27
  • Commits 1
  • Pipelines 25
  • Changes 12

Cilium is a container networking provider that can be used to enable support for NetworkPolicy in a cluster.

Supports installation to both GKE (default) and EKS via clusterType variable.

Unfortunately cilium is not working with k3s due to difference in IPAM/CIDR management. I will do more testing around it but for now I think it will be better to disable it on k3s.

I had to introduce 2 new stages to the CI pipeline (cilium_install and cilium_uninstall) to make necessary kube-system pod restarts on GKE. Without those kube-system pods might be unavailable and helm will fail to reach metrics endpoints. Restarts are necessary since cilium's node init daemonset will reconfigure kubelet to use it's CNI plugin and this might cause some pods (notably kube-dns) to use cilium's IPAM.

I'm temporary serving helm charts from the defend's group repository since cilium doesn't have helm repository. Cilium devs aim to deploy helm repository in upcoming major release which supposed to happen before 12.6.

related to gitlab-org/gitlab#14010 (closed)

Edited Dec 12, 2019 by Arthur Evstifeev
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: cilium-cluster-application

Enable Gitpod?

To use Gitpod you must first enable the feature in the integrations section of your user preferences.

Cancel Enable Gitpod