[CHEF-16732] Pipelines to build the client with habitat and deploy to chef/chef-hab docker repo

[ashiqueps]

Description

With Chef Infra Client 19, the omnibus builds are disabled and available through Habitat only. As a result, the pipelines that created the chef/chef docker image were commented out.

In this PR, I've updated the Dockerfile to build the chef-infra-client using the habitat and updated the pipelines to build it and deploy it to a different repo called chef/chef-hab.

The difference between the old chef/chef and chef/chef-hab is that chef/chef contains the omnibus version of the chef-infra-client 18 and the earlier versions where as the chef/chef-hab will contain the habitat version of chef-infra-client and newer versions.

Note:
Currently, the docker images are built for the amd64 arch only. The pipelines for arm64 have been commented out and will be added back once we have support for arm64 in chef habitat.

Related Issue

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

• I have read the CONTRIBUTING document.
• I have run the pre-merge tests locally and they pass.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
• All new and existing tests passed.
• All commits have been signed-off for the Developer Certificate of Origin.

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sean-sype-simmons]

Looking through this, I think most of this is valid, but we will need to also update the community and internal developers how this affects things like kitchen, and or habitat. Things to consider updating:

chef/kitchen-tests/README.md

Line 7 in 545f089

These tests run in Docker containers, so make sure to install Docker on your workstation. Once Docker is installed, all the gems needed to run these tests can be installed with Bundler.

chef/docs/dev/design_documents/how_chef_is_tested_and_built.md

Line 18 in 545f089

- Full Test Kitchen integration tests that covers common Chef usage on various different Linux Distros. Those integration tests run using the kitchen-dokken plugin and the dokken-images Docker containers, which do their best to replicate a real Linux system. You can see exactly what we test here: https://github.com/chef/chef/blob/main/kitchen-tests/cookbooks/end_to_end/recipes/default.rb

chef/docs/dev/how_to/adding_new_platforms_to_infra.md

Line 15 in 545f089

For major new Linux or Windows distribution releases, you'll want to add these to the RubyDistros repository. You can test these builds locally in Docker and then set the builds to run on DockerHub. If you're not a member of the [RubyDistros DockerHub org](https://hub.docker.com/orgs/rubydistros) then ask #releng-support to add you to that. From there you can add a new repository matching the existing repository setups. Make sure you configure the automated builds to point to the correct Dockerfile path with each Ruby version as a tag. See https://hub.docker.com/repository/docker/rubydistros/opensuse-15 for an example of how we set this up.

chef/docs/dev/ci/README.md

Line 9 in 545f089

- [Docker Container Platforms](#docker-container-platforms)

Do we also want to produce a windows docker image based on the same work?

[sean-sype-simmons]

taking sometime to verify all this and looking through configurations on expeditor.

[Stromweld]

why are we switching docker hub org to chef-hab? Customers know that chef-ciient 19 is hab built package and having it in the same docker hub org chef/chef should be fine then. Just like any update they know major versions have changes in them like in this case 19 will be hab built version in the container.

[PrajaktaPurohit]

@Stromweld Pushing the hab images in the same repo as chef/chef will break the test-kitchen drivers. They currently set the path based on the repo that the image is being pulled from.

[jaymzh]

Sean mentioned this is still WIP.

[johnmccrae]

@ashiqueps do we still need this? Can I close this?

[rahulgoel1]

@johnmccrae yes this is needed. @ashiqueps can you pls rebase.?

[sean-sype-simmons]

lgtm , thanks for handling this.

[tpowell-progress]

Note the arm64 disabling on the main page, when it should be restored, and the changes to path that has been made.

[rahulgoel1]

@ashiqueps Arm support will be have to added once habitat has support for arm released. Can you pls add that in description for the PR. Arm release for hab should be planned in coming months.

[ashiqueps]

@rahulgoel1, @tpowell-progress Updated the PR description and the code comments. Please review.

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud