make network policies necessary

[halamix2]

Description

Changes proposed in this pull request:

• make network policies necessary
• remove enableNetworkPolicies flag

Related issue(s)

• Serverless internal network policies should be always enabled #2068

[hyperspace-insights]

Summary

The following content is AI-generated and provides a summary of the pull request:

---

Make Network Policies Mandatory for Serverless Module

Changes

This pull request enforces network policies for the Serverless module by making them always enabled and removing the user-configurable flag.

Key Modifications

• API Changes:

  • components/operator/api/v1alpha1/serverless_types.go: Removed EnableNetworkPolicies field from ServerlessSpec and NetworkPoliciesEnabled field from ServerlessStatus
  • config/operator/base/crd/bases/operator.kyma-project.io_serverlesses.yaml: Updated CRD definitions to remove network policies configuration fields

• Operator Logic:

  • components/operator/internal/state/controller_configuration.go: Modified state machine to skip network policies configuration step and proceed directly to resource application
  • components/operator/internal/state/network_policies.go: Removed (network policies configuration logic no longer needed)
  • components/operator/internal/state/network_policies_test.go: Removed (associated tests)
  • components/operator/internal/chart/flags.go: Removed WithEnableNetworkPolicies method from flags builder
  • components/operator/internal/chart/flags_test.go: Updated tests to remove network policies flag assertions

• Helm Charts:

  • config/buildless-serverless/templates/network-policies.yaml: Removed conditional wrapper - network policies now always deployed
  • config/buildless-serverless/values.yaml: Removed networkPolicies.enabled configuration option
  • config/serverless/templates/network-policies.yaml: Removed conditional wrapper
  • config/serverless/values.yaml: Removed networkPolicies.enabled configuration option

• UI Extensions:

  • config/operator/base/ui-extensions/serverless/details: Removed status.networkPoliciesEnabled display field
  • config/operator/base/ui-extensions/serverless/form: Removed spec.enableNetworkPolicies form field
  • config/operator/base/ui-extensions/serverless/translations: Removed translations for network policies fields

• CI/CD:

  • .github/workflows/_integration-tests.yaml:
    • Removed duplicate integration test jobs (legacy-git-auth-integration-with-network-policies-test and git-auth-integration-with-network-policies-test)
    • Standardized quote style in workflow input descriptions
    • Cleaned up BTP integration test configuration

• Documentation:

  • docs/user/00-20-configure-serverless.md: Removed section about enabling network policies since they are now always enabled

• Sample Configurations:

  • config/samples/legacy-serverless-with-networkpolicies-enabled.yaml: Removed (no longer needed)
  • config/samples/serverless-with-networkpolicies-enabled.yaml: Removed (no longer needed)

• Tests:

  • tests/operator/serverless/verify.go: Removed validation logic for network policies status field

• CRD Updates:

  • config/serverless/config/crd/bases/serverless.kyma-project.io_functions.yaml: Added metadata to required fields list

GitHub Issues

• #2068: Serverless internal network policies should be always enabled

---

• 🔄 Regenerate and Update Summary
• ✏️ Insert as PR Description (deletes this comment)
• 🗑️ Delete comment

PR Bot Information

Version: 1.16.24

• LLM: anthropic--claude-4.5-sonnet
• Event Trigger: pull_request.opened
• Correlation ID: 4cfb9200-d756-11f0-9169-ec014ca4eb0d
• GithubContextProvider: Serverless internal network policies should be always enabled #2068
• GithubContextProvider: Test the serverless module with the latest Kubernetes API supported by gardener #43
• Summary Prompt: Default Prompt
• GithubContextProvider: Fix orphan check #123
• Output Template: Default Template
• GithubContextProvider: Prepare customer-facing documentation for Serverless Manager #33

---

💌 Have ideas or want to contribute? Create an issue and share your thoughts with us!
📑 Check out the documentation for more information.

Made with ❤️ by Hyperspace.

[kwiatekus]

Additionally, please also make sure that the integration tests are executed on cluster where deny-all policy is apoplied in kyma-system