Skip to content

Commit e95812d

Browse files
committed
address review comments
1 parent e9799d3 commit e95812d

File tree

2 files changed

+3
-6
lines changed

2 files changed

+3
-6
lines changed

docs/iaas/usage-guides/ipam.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
# IPAM Resources
2+
23
This guide explains how to use IronCore's integrated IP address management (IPAM) resources to define and manage IP prefixes and allocations.
34

45
## Prefix

docs/iaas/usage-guides/networking.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Networking Resources
22

3-
This guide describes the core networking resources in IronCore, such as `Networks`, `NetworkInterfaces`, `VirtualIPs`, `NAT gateways`, `LoadBalancers`, and `NetworkPolicies`. It explains how to define, configure, and manage these resources for the infrastructure.
3+
This guide describes the core networking resources in IronCore, such as `Networks`, `NetworkInterfaces`, `VirtualIPs`, `NAT gateways`, `LoadBalancers`, and `NetworkPolicies`.
44

55
## Network
66

@@ -27,10 +27,9 @@ spec:
2727
2828
- `peerings` (`list`): Are the list of network peerings with this `Network` (optional).
2929

30-
3130
### More about IronCore Network:
3231

33-
- **Network creation**: [ironcore-net](https://github.com/ironcore-dev/ironcore-net) is the network plugin for IronCore that realizes the `Network` resource, When an IronCore `Network` is created, a corresponding `core.apinet.ironcore.dev/Network` is created in the ironcore-net(apinet) cluster.
32+
- **Network creation**: [ironcore-net](https://github.com/ironcore-dev/ironcore-net) is the network plugin for IronCore that realizes the `Network` resource. When an IronCore `Network` is created, a corresponding `core.apinet.ironcore.dev/Network` is created in the ironcore-net(apinet) cluster.
3433
Once created and with an allocated ID, the IronCore `Network` will be patched with the corresponding providerID of the apinet Network and set to state: `Available`.
3534
The format of a network providerID is as follows:
3635
`ironcore-net://<namespace>/<name>/<id>/<uid>`
@@ -61,7 +60,6 @@ status:
6160
- name: peering1
6261
state: Ready
6362
state: Available
64-
6563
```
6664

6765
For detailed e2e example on network peering
@@ -73,7 +71,6 @@ A `NetworkInterface` resource in IronCore represents a connection point between
7371
network. It encapsulates the configuration and life cycle management of the virtual network interface, ensuring
7472
seamless connectivity for `Machines`.
7573

76-
7774
### Example NetworkInterface Resource
7875

7976
An example of how to define a `NetworkInterface` resource in IronCore:
@@ -179,7 +176,6 @@ spec:
179176
- `portsPerNetworkInterface` (`int32`): This Specifies the number of ports allocated per network interface and controls how many simultaneous connections can be handled per interface. If empty, 2048 (DefaultPortsPerNetworkInterface) is the default.
180177
- `networkRef` (`string`): It represents which network this `NATGateway` serves.
181178

182-
183179
After reconciling all `NATGateways`, the status gets updated with the corresponding values for `ips` as shown below.
184180

185181
```yaml

0 commit comments

Comments
 (0)