skills.rest
kube-dc
kube-dcOFFICIAL
Explore all skills by this author →
WebsiteGitHub

manage-networking

Create EIPs and FIPs and inspect VPC networks for Kube-DC projects.

34|5|Updated Mar 5, 2025
Search Tags:#networking#cloud#vpc#eip#kube-dc#fip#kubedc
One-click install
npx skills add https://github.com/kube-dc/kube-dc-public --skill manage-networking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manage-networking
Source: https://github.com/kube-dc/kube-dc-public/tree/main/skills/manage-networking
Command: npx skills add https://github.com/kube-dc/kube-dc-public --skill manage-networking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kube-DC networking administration is simplified by providing a clear model for allocating External IPs, Floating IPs, and managing per-project VPC networking to control exposure and reachability.

Core Features & Use Cases

  • Create and manage EIPs (External IPs) to expose services via LoadBalancer without exposing pods directly.
  • Create and manage FIPs (Floating IPs) to provide direct, 1:1 public IP access to VMs or pods.
  • Understand and configure per-project VPC networking, including namespace isolation and gateway considerations.

Quick Start

Create an External IP and a Floating IP for a project, then verify connectivity.

Frequently Asked Questions about manage-networking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I allocate external IPs in Kube-DC to expose services without exposing pods directly?▼

To allocate external IPs in Kube-DC, you create EIPs that expose services via LoadBalancer. This provides external access while keeping underlying pods isolated from direct public reachability.

What is the difference between EIPs and Floating IPs for VM networking?▼

EIPs expose services via LoadBalancer without exposing pods directly, whereas FIPs provide direct 1:1 public IP access to VMs or pods for specific external communication requirements.

How do I map a Floating IP to a VM interface in a Kube-DC VPC?▼

You map Floating IPs to VM interfaces by configuring FIPs within your Kube-DC networking strategy. This provides direct 1:1 public IP access to the targeted virtual machines.

Does Kube-DC networking support per-project VPC isolation and gateway configuration?▼

Yes, Kube-DC networking supports per-project VPC configuration, including namespace isolation and gateway considerations, to effectively control network exposure and reachability across projects.

What are the limitations when managing EIP and FIP quotas in Kube-DC?▼

Managing EIP and FIP quotas requires validating your resource limits before allocation. Safe configuration of these IP resources depends on strict quota validation to prevent allocation failures.

Related Skills

Explore More Software Engineering Skills→
haxlyshaxlys

k8s-security-policies

Generate and enforce Kubernetes NetworkPolicy, PodSecurityPolicy, and RBAC security policies.

Community
Advanced
apecloudapecloud
3

kubeblocks-expose-service

Expose KubeBlocks database services via LoadBalancer or NodePort OpsRequests.

Official
Intermediate
kube-dckube-dc
34

ssh-into-vm

Automate SSH access to Kube-DC VMs using project keys and discovered IPs.

Official
Intermediate
adaptive-enforcement-labadaptive-enforcement-lab
3

network-security

Configure GKE networking with VPC-native IP allocation and zero-trust policies.

Official
Advanced