# Create Guard to Allow Egress with IP/CIDR

Create guard to allow egress with IP/CIDR is used to create a CloudekaGuard that will allow outbound traffic (egress) from pods with certain labels to the specified IP address or IP range (CIDR). Using this script, you can control outbound access from pods labeled app:client-default in the ns1 namespace to permitted IP addresses or IP ranges, and even exclude certain sub-chains from larger IP ranges. This helps limit access to unwanted resources and improves security. You can first run the following syntax to create a YAML file with the name allow-egress-with-cidr.

```bash
nano allow-egress-with-cidr.yaml
```

Copy and paste the following YAML contents.

```yaml
apiVersion: tenants.cloudeka.ai/v1alpha2
kind: CloudekaGuard
metadata:
  name: allow-egress-with-port
  namespace: ns1
spec:
  endpointSelector:
    matchLabels:
      app: client-default
  egress:
  - fromCIDR:
    - 192.168.1.100/32
  - fromCIDRSet:
    - cidr: 192.168.0.0/16
      except:
      - 192.168.1.0/24
```

After pasting the syntax, save the file by pressing Ctrl + O, then press the Enter key and exit the editor by pressing Ctrl + X. The next step is to apply for the Cloudeka Guard.

```bash
kubectl apply -f allow-egress-with-cidr.yaml
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cloudeka.ai/guidance-for-individual/deka-gpu/deka-gpu-security/deka-guard/create-guard-to-allow-egress-with-ip-cidr.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.