mirror of
https://github.com/nubenetes/awesome-kubernetes.git
synced 2026-08-18 03:46:27 +00:00
MLOps Poll
This commit is contained in:
@@ -104,6 +104,7 @@ Let's improve both the private & public IT sector and the opportunities in large
|
||||
USA (4 Million).
|
||||
India (2.2 Million).
|
||||
</center>
|
||||
|
||||
## Stats
|
||||
<details>
|
||||
<summary>Stats 1. Click to expand!</summary>
|
||||
|
||||
+3
-1
@@ -175,12 +175,14 @@
|
||||
## Git Repositories Structures
|
||||
- [==dzone: GitOps: How to Ops Your Git the Right Way== 🌟](https://dzone.com/articles/gitops-how-to-ops-your-git-the-right-way) In this article we’ll look into the specifics of creating Git repositories structures — the very core of the GitOps approach.
|
||||
- [==codefresh.io: Stop Using Branches for Deploying to Different GitOps Environments==](https://codefresh.io/about-gitops/branches-gitops-environments/) How do I promote a release to the next environment? **You should NOT use Git branches for modeling different environments. If the Git repository holding your configuration (manifests/templates in the case of Kubernetes) has branches named “staging”, “QA”, “Production” and so on, then you have fallen into a trap.** Using branches for different environments should only be applied to legacy applications.
|
||||
- [==developers.redhat.com: Git best practices: Workflows for GitOps deployments== 🌟](https://developers.redhat.com/articles/2022/07/20/git-workflows-best-practices-gitops-deployments)
|
||||
- [==developers.redhat.com: Git best practices: Workflows for GitOps deployments | Christian Hernandez== 🌟](https://developers.redhat.com/articles/2022/07/20/git-workflows-best-practices-gitops-deployments)
|
||||
- Separate your repositories
|
||||
- Separate development in directories, not branches
|
||||
- Trunk-based development
|
||||
- Pay attention to policies and security
|
||||
|
||||
- [==developers.redhat.com: How to set up your GitOps directory structure | Christian Hernandez== 🌟](https://developers.redhat.com/articles/2022/09/07/how-set-your-gitops-directory-structure)
|
||||
|
||||
## GitOps Tools
|
||||
- [FluxCD, ArgoCD or Jenkins X: Which Is the Right GitOps Tool for You?](https://blog.container-solutions.com/fluxcd-argocd-or-jenkins-x-which-is-the-right-gitops-tool-for-you)
|
||||
- [slideshare: GitOps, Jenkins X & Future of CI/CD](https://slideshare.net/rakutentech/gitops-jenkins-x-future-of-cicd)
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 311 KiB |
+11
-3
@@ -11,6 +11,7 @@
|
||||
- [Samples](#samples)
|
||||
- [ML Courses](#ml-courses)
|
||||
- [ML Competitions and Challenges](#ml-competitions-and-challenges)
|
||||
- [Polls](#polls)
|
||||
- [Tweets](#tweets)
|
||||
## Introduction. MLOps
|
||||
- [cd.foundation: Announcing the CD Foundation MLOps SIG](https://cd.foundation/blog/2020/02/11/announcing-the-cd-foundation-mlops-sig/)
|
||||
@@ -84,8 +85,8 @@
|
||||
## Azure ML
|
||||
- [docs.microsoft.com: MLflow and Azure Machine Learning](https://docs.microsoft.com/en-us/azure/machine-learning/concept-mlflow) One of the open-source projects that has made #ML better is MLFlow. Microsoft is expanding support for APIs, no-code deployment for MLflow models in real-time/batch managed inference, curated MLflow settings, and CLI v2 integrations.
|
||||
- [bea.stollnitz.com: Creating batch endpoints in Azure ML](https://bea.stollnitz.com/blog/aml-batch-endpoint/)
|
||||
- Suppose you’ve trained a machine learning model to accomplish some task, and you’d now like to provide that model’s inference capabilities as a service. Maybe you’re writing an application of your own that will rely on this service, or perhaps you want to make the service available to others. This is the purpose of endpoints — they provide a simple web-based API for feeding data to your model and getting back inference results.
|
||||
- Azure ML currently supports three types of endpoints: batch endpoints, Kubernetes online endpoints, and managed online endpoints. I’m going to focus on batch endpoints in this post, but let me start by explaining how the three types differ.
|
||||
- Suppose you’ve trained a machine learning model to accomplish some task, and you’d now like to provide that model’s inference capabilities as a service. Maybe you’re writing an application of your own that will rely on this service, or perhaps you want to make the service available to others. This is the purpose of endpoints — they provide a simple web-based API for feeding data to your model and getting back inference results.
|
||||
- Azure ML currently supports three types of endpoints: batch endpoints, Kubernetes online endpoints, and managed online endpoints. I’m going to focus on batch endpoints in this post, but let me start by explaining how the three types differ.
|
||||
|
||||
## KServe Cloud Native Model Server
|
||||
- [kserve.github.io](https://kserve.github.io/website/0.8/) Highly scalable and standards based Model Inference Platform on Kubernetes for Trusted AI
|
||||
@@ -116,6 +117,13 @@
|
||||
- [Kaggle Competitions](https://www.kaggle.com/competitions)
|
||||
- [isic-archive.com](https://www.isic-archive.com/#!/topWithHeader/wideContentTop/main)
|
||||
|
||||
## Polls
|
||||
??? note "Click to expand!"
|
||||
|
||||
<center>
|
||||
[](https://www.linkedin.com/feed/update/urn:li:activity:6923979009311559680)
|
||||
</center>
|
||||
|
||||
## Tweets
|
||||
<details>
|
||||
<summary>Click to expand!</summary>
|
||||
@@ -135,4 +143,4 @@
|
||||
|
||||
<blockquote class="twitter-tweet"><p lang="en" dir="ltr"><a href="https://twitter.com/kelseyhightower?ref_src=twsrc%5Etfw">@kelseyhightower</a> We're now at a stage where we can start to leverage systems like <a href="https://twitter.com/hashtag/Flyte?src=hash&ref_src=twsrc%5Etfw">#Flyte</a> to give us more of an opinionated end-to-end workflow. What we call <a href="https://twitter.com/hashtag/ML?src=hash&ref_src=twsrc%5Etfw">#ML</a> can become a real discipline where practitioners can use a common set of terms and practices.<a href="https://twitter.com/hashtag/KelseyTakesFlyte?src=hash&ref_src=twsrc%5Etfw">#KelseyTakesFlyte</a> <a href="https://twitter.com/hashtag/MLOps?src=hash&ref_src=twsrc%5Etfw">#MLOps</a></p>— Flyte (@flyteorg) <a href="https://twitter.com/flyteorg/status/1550543758764044288?ref_src=twsrc%5Etfw">July 22, 2022</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
|
||||
</center>
|
||||
</details>
|
||||
</details>
|
||||
|
||||
@@ -432,6 +432,7 @@
|
||||
|
||||
#### Azure Terrafy and AzAPI Terraform Provider
|
||||
- [==Announcing Azure Terrafy and AzAPI Terraform Provider Previews==](https://techcommunity.microsoft.com/t5/azure-tools-blog/announcing-azure-terrafy-and-azapi-terraform-provider-previews/ba-p/3270937) On Azure, businesses may choose many flavors of IaC tooling to manage their Azure resources including HashiCorp Terraform, Bicep, ARM templates, Ansible and many more. We encourage you to choose the IaC tool that best suits your needs. Our mission is to ensure that no matter which tool you choose, you have the best experience and integration with Azure.
|
||||
- [techcommunity.microsoft.com: Azure Terrafy – Import your existing Azure infrastructure into Terraform HCL](https://techcommunity.microsoft.com/t5/itops-talk-blog/azure-terrafy-import-your-existing-azure-infrastructure-into/ba-p/3357653)
|
||||
|
||||
#### Terraform in Azure DevOps
|
||||
- [==adamtheautomator.com: How to Build Infrastructure with Terraform in Azure DevOps== 🌟](https://adamtheautomator.com/terraform-azure-devops/)
|
||||
|
||||
Reference in New Issue
Block a user