Skip to content

Commit

Permalink
remove non-core function point
Browse files Browse the repository at this point in the history
  • Loading branch information
network-charles committed Jun 24, 2024
1 parent f7c5279 commit fa7a54f
Showing 1 changed file with 0 additions and 23 deletions.
23 changes: 0 additions & 23 deletions site/content/en/docs/technical-outcomes/simulation.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,29 +42,6 @@ page. But in a KWOK cluster, you get nothing because the pod isn't real.
- **PortForward:** [Port forwarding](https://kwok.sigs.k8s.io/docs/user/port-forward-configuration/#clusterportforward), which establishes a direct connection to a container port, can be simulated
for a single pod or multiple pods.

3. **Recording the creation of a Kubernetes cluster:** The running cluster can be recorded, and its content saved as a YAML output.
This can be valuable for these reasons:

- **Documentation and Reproducibility:** By recording the steps taken to create the cluster, you essentially
create documentation for future reference. This documentation can be useful for understanding how the cluster
was set up, what configurations were applied, and how different components were integrated. It also helps in
reproducing the cluster setup in other environments.
- **Troubleshooting and Debugging:** If any issues arise with the cluster later on, having a record of its
creation can be helpful in troubleshooting and debugging. You can refer back to the recorded steps to identify
any misconfigurations or errors that might be causing problems.
- **Auditing and Compliance:** In environments where auditing and compliance are important, having a record of
the cluster creation process can be essential. It provides transparency into the changes made to the
infrastructure and ensures that the cluster was set up according to organizational policies and standards.
- **Training and Education:** Recording the creation of a Kubernetes cluster can also serve as educational
material for team members learning about Kubernetes or onboarding new team members. They can follow along
with the recorded steps to understand how the cluster was deployed and configured.
- **Reproducibility and Disaster Recovery:** In the event of a disaster or the need to recreate the cluster due
to changes in requirements or infrastructure failures, having a recorded snapshot of the cluster creation
process makes it easier to reproduce the cluster quickly and accurately.

Overall, recording the creation of a Kubernetes cluster provides a range of benefits, including documentation,
troubleshooting, compliance, education, and disaster recovery.

## Applications and Use Cases

1. **Scheduler Simulation:** Beyond the default Kubernetes scheduler, developers build custom schedulers
Expand Down

0 comments on commit fa7a54f

Please sign in to comment.