Make metal3 helm chart compatible with the Sylva project

[ipetrov117]

This PR introduces changes that enable the metal3-deploy helm chart to be successfully deployed within the Sylva project.

---

Changes related to the MariaDB chart:

1. MariaDB service no longer requires a hardcoded clusterIP for it to function.

Commits:

• 307429075b1e164fc4e4b9f38db3c0089d930a06

---

Changes related to the Ironic chart:

1. Ironic's deployment templatization has been improved
2. Ironic now communicates with MariaDB over the service FQDN
3. Extend Ironic's service templatization

Commits:

• 2598fdfeefbce602d8da96aa1afd41d2044a6b08

---

Changes related to the Baremetal-operator chart:

1. Templated security context for the BMO deployment
2. Included clusterctl.cluster.x-k8s.io label to all CRDs in order to ensure that they can be pivoted when doing clusterctl move
3. Removed unnecessary configurations from the BMO ConfigMap

Commits:

• 767cd0ff590bd4dcb474e778582f70418c6356d8
• 1ed5aae4fc36c3e9a31323800a301284839edfbe
• 07b97b2757816e1d1f5c8fabe85ac71a255cf3cd

[hardys]

Overall this looks good, but in future IMHO it would be much better to break changes like this into several PRs since it contains several logically unrelated changes - this would be far easier/faster to review.

The main issue I see is the DATABASE_HOST change is backwards incompatible and won't work with the default chart configuration - I think that means we either add a conditional for emptydatabase_clusterIP or rebase on #37 which solves the underlying problem by removing the special dnsConfig from the Ironic Pod.

[ipetrov117]

Overall this looks good, but in future IMHO it would be much better to break changes like this into several PRs since it contains several logically unrelated changes - this would be far easier/faster to review.

The main issue I see is the DATABASE_HOST change is backwards incompatible and won't work with the default chart configuration - I think that means we either add a conditional for emptydatabase_clusterIP or rebase on #37 which solves the underlying problem by removing the special dnsConfig from the Ironic Pod.

I mentioned it on #38, but just to cover here also. Merging #37 and #38 in 0.2.0 first would greatly benefit this PR. Furthermore by doing this we will keep 0.1.0 backwards compatible.

[ipetrov117]

Overall this looks good, but in future IMHO it would be much better to break changes like this into several PRs since it contains several logically unrelated changes - this would be far easier/faster to review.
The main issue I see is the DATABASE_HOST change is backwards incompatible and won't work with the default chart configuration - I think that means we either add a conditional for emptydatabase_clusterIP or rebase on #37 which solves the underlying problem by removing the special dnsConfig from the Ironic Pod.

I mentioned it on #38, but just to cover here also. Merging #37 and #38 in 0.2.0 first would greatly benefit this PR. Furthermore by doing this we will keep 0.1.0 backwards compatible.

#37 and #38 have been merged and this PR has been rebased on top of them in the 0.2.0 version. Furthermore I added the missing packages needed to build the metal3 artefacts with the current changes.

[hardys]

Overall lgtm - couple of small comments/questions related to the configurable values.

[ipetrov117]

Overall lgtm - couple of small comments/questions related to the configurable values.

Change suggestions have been addressed.