Muhammet Arslan iammuho

Steps for Configuring EKS with VPC CNI Custom Networking

Install the EKS Addon VPC CNI addon.
Ensure a secondary CIDR block is attached to the VPC (already done).
Ensure private subnets use the secondary CIDR block (already done).
Retrieve the cluster security group ID, the VPC ID, and subnet IDs from the AWS Management Console.

	<!DOCTYPE html>
	<meta charset="utf-8">
	<style>
	.node {
	font: 300 11px "Helvetica Neue", Helvetica, Arial, sans-serif;
	fill: #bbb;
	}
	.node:hover {
	fill: #000;
	}

	apiVersion: backstage.io/v1alpha1
	kind: Group
	metadata:
	name: tribe-a
	namespace: company
	description: This is tribe-a tribe of company
	spec:
	type: tribe
	profile:
	displayName: Tribe A

	using System.Collections;
	using System.Collections.Generic;
	using UnityEngine;

	public class MyScript : MonoBehaviour
	{
	[SerializeField] GameObject item;
	// Start is called before the first frame update
	void Start()
	{

	---
	# Create the service account scoped to our `actions-runner-system` namespace
	apiVersion: v1
	kind: ServiceAccount
	metadata:
	name: gh-actions-deploy
	namespace: actions-runner-system
	secrets:
	- name: gh-actions-deploy

	apiVersion: crd.k8s.amazonaws.com/v1alpha1
	kind: ENIConfig
	metadata:
	name: $az_1
	spec:
	securityGroups:
	- $cluster_security_group_id
	subnet: $new_subnet_id_1
	---
	apiVersion: crd.k8s.amazonaws.com/v1alpha1

	# Project Setup Guide

	This document outlines the steps taken to configure and deploy a Kubernetes environment utilizing an AWS Load Balancer and NGINX Ingress Controller via Helm charts.

	## Step 1: Create a New Helm Chart

	A new Helm chart is created to function as a wrapper, allowing the deployment of the AWS Load Balancer and NGINX Ingress Controller Helm charts together. This setup uses Helm's dependency management capabilities.

	### Chart Details