blog: odo with .NET and PostgreSQL on OpenShift

[kadel]

/area documentation

Start converting some old .NET guides to odo v3, and in the process, I realized that this might be a nice blog post for odo.

This guide shows how container-overrides can be leveraged. I think that this could become one of the most important devfile/odo features.

Things to do before merging/publishing:

• thorough review language review
• it requires Update devfile/library to support pod-overrides and container-overrides attributes and add integration test for it #6512 to be merged and released
• I want to include a quick gif or video (no more than 1,5 minutes) of a terminal running all the steps to highlight how easy it can be.

NOTE:
I was also thinking about breaking this into two posts. One just runs the application with an in-memory database. Then the follow-up post with the PostgreSQL.

[netlify]

✅ Deploy Preview for odo-docusaurus-preview ready!

Name	Link
🔨 Latest commit	dc990cd
🔍 Latest deploy log	https://app.netlify.com/sites/odo-docusaurus-preview/deploys/63f6071720179c000832d25c
😎 Deploy Preview	https://deploy-preview-6500--odo-docusaurus-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[odo-robot]

OpenShift Tests on commit b0ec29d finished with errors.
View logs: TXT HTML

[odo-robot]

NoCluster Tests on commit b0ec29d finished with errors.
View logs: TXT HTML

[odo-robot]

Unit Tests on commit b0ec29d finished successfully.
View logs: TXT HTML

[odo-robot]

Validate Tests on commit b0ec29d finished successfully.
View logs: TXT HTML

[odo-robot]

Kubernetes Tests on commit b0ec29d finished with errors.
View logs: TXT HTML

[odo-robot]

Windows Tests (OCP) on commit b0ec29d finished with errors.
View logs: TXT HTML

[feloy]

Suggested change

	Now, refresh the local URL [http://localhost:40001](http://localhost:40001). You should see that our application is using the PostgreSQL database.
	Now, refresh the local URL [http://localhost:20001](http://localhost:20001). You should see that our application is using the PostgreSQL database.

[rm3l]

Nice tutorial. I added a few comments and suggestions.

[rm3l]

I found 2 minor typos to fix, but LGTM overall.

[kadel]

updated, now it should be ready for publishing.
Thx, @feloy and @rm3l for reviews

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[rm3l]

/override Kubernetes-Integration-Tests/Kubernetes-Integration-Tests
/override NoCluster-Integration-tests/NoCluster-Integration-tests
/override OpenShift-Integration-tests/OpenShift-Integration-tests
/override OpenShift-Integration-tests/OpenShift-Unauth-Integration-tests
/override windows-integration-test/Windows-test

Overriding because this is a doc-only PR. It was still interesting to see why all those tests failed.
They seem to have failed because of the update notification being displayed in the odo output. Some of the tests are currently making strict assertions on the output. The issue has been reported in #6618

[openshift-ci]

@rm3l: Overrode contexts on behalf of rm3l: Kubernetes-Integration-Tests/Kubernetes-Integration-Tests, NoCluster-Integration-tests/NoCluster-Integration-tests, OpenShift-Integration-tests/OpenShift-Integration-tests, OpenShift-Integration-tests/OpenShift-Unauth-Integration-tests, windows-integration-test/Windows-test

In response to this:

/override Kubernetes-Integration-Tests/Kubernetes-Integration-Tests
/override NoCluster-Integration-tests/NoCluster-Integration-tests
/override OpenShift-Integration-tests/OpenShift-Integration-tests
/override OpenShift-Integration-tests/OpenShift-Unauth-Integration-tests
/override windows-integration-test/Windows-test

Overriding because this is a doc-only PR. It was still interesting to see why all those tests failed.
They seem to have failed because of the update notification between displayed in the odo output. Some of the tests are currently making strict assertions on the output. The issue has been reported in #6618

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.