oke-gva-deployer

Generate OCI CLI commands to deploy OKE node pools with GVA profiles.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/chiphwang1/oke-agent-plugin-improvement --skill oke-gva-deployer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oke-gva-deployer
Source: https://github.com/chiphwang1/oke-agent-plugin-improvement/tree/main/skills/oke-gva-deployer
Command: npx skills add https://github.com/chiphwang1/oke-agent-plugin-improvement --skill oke-gva-deployer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires oci, kubectl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the complex process of configuring and deploying Oracle Kubernetes Engine (OKE) node pools with Generic VNIC Attachments (GVA), enabling advanced network segmentation and resource isolation for your workloads.

Core Features & Use Cases

  • GVA Configuration: Guides users through setting up secondary VNICs with custom subnets, NSGs, and IP addressing for specific application resources.
  • Node Pool Deployment: Generates OCI CLI commands to create or update OKE node pools with GVA profiles.
  • Workload Scheduling: Provides sample manifests for pods that request GVA resources and includes necessary tolerations for scheduling.
  • Use Case: Deploy a new OKE node pool where specific pods need dedicated network interfaces for sensitive data processing, ensuring network isolation and compliance.

Quick Start

Use the oke-gva-deployer skill to configure and create a new OKE node pool with secondary VNIC profiles.

Frequently Asked Questions about oke-gva-deployer

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

FAQPage Schema
How do I configure OKE node pools with secondary VNICs for network isolation?

You can configure OKE node pools with secondary VNICs by setting up Generic VNIC Attachments (GVA) with custom subnets and NSGs. This provides workload isolation and ensures network segmentation for sensitive data processing.

What is Generic VNIC Attachment in Oracle Kubernetes Engine?

Generic VNIC Attachment (GVA) in Oracle Kubernetes Engine is a feature that allows secondary VNIC profiles to be attached to node pools. It enables advanced network segmentation by allocating dedicated network interfaces and custom IP addressing to specific pods.

How do I deploy an OKE node pool using OCI CLI commands for GVA?

To deploy an OKE node pool with GVA, you need to generate and execute OCI CLI commands that define secondary VNIC profiles, custom subnets, and NSGs. This automates the creation of node pools with advanced network segmentation.

Can I schedule Kubernetes pods to specific secondary VNICs in OKE?

Yes, you can schedule pods to specific secondary VNICs by using sample manifests that request GVA resources and include necessary tolerations. This ensures workloads are scheduled on nodes with the correct dedicated network interfaces.

Does OKE Generic VNIC Attachment work with custom Network Security Groups?

Yes, OKE Generic VNIC Attachment works with custom Network Security Groups (NSGs). The configuration guides you through setting up secondary VNICs with custom subnets and NSGs to enforce strict compliance and network segmentation.

When do I need to use secondary VNIC profiles in OKE?

You need secondary VNIC profiles in OKE when specific pods require dedicated network interfaces for sensitive data processing. This approach facilitates workload isolation and ensures strict compliance through network segmentation.