equinix-labs / metal-iot

An IoT showcase for the power of bare metal compute and Sprint Curiosity 5G Network

Equinix Labs

• See Getting Started for a quick guide to creating a repo.
• See Purpose and Governance to learn about Equinix Labs and to find out how you can contribute to it.
• See Uniform Standards to learn about the tiers of project fitness.
• See Terraform Modules to learn how to prepare, review, and publish Terraform Modules for Equinix Terraform providers.

metal-iot's Issues

Project depends on Packet CSI

The Packet CSI project and service are no longer available. A different storage provider should be used.

StorageClass is incorrect

Hi folks,

After merging #14 from @c0dyhi11 the StorageClass is now incorrect in the emitter configuration and possibly in KubeDB.

Please consider updating to the built-in storage class of k3s which is the local-path-provisioner:

kubectl get StorageClass
NAME                   PROVISIONER             AGE
local-path (default)   rancher.io/local-path   16m

For example: https://github.com/packet-labs/iot/blob/master/emitter/broker.yaml#L57

packet-labs/iot will be removed!

This repository will be deleted by November 1, 2021.

While the concepts and instruction provided in this repository may be helpful to some users and carry some relevance, this repository has seen few recent changes. Packet became Equinix Metal over a year ago.

This repository requires maintenance and owners to ensure that the documentation is up to date and relevant. A repository like this one may need to update the version of dependencies and tools for safe consumption.

If you are affected by this deletion, please comment by the November 1, 2021 date.

Alternatives:

• Repo is Archived. This is not preferable, it is intended that the 'packet-labs' GH org is vacated.
• Repo is moved to github.com/equinix-labs. This is only preferably after Packet branding and tooling has been updated to Equinix Metal.

update `minimist` dependency

#75 describes a dependency upgrade identified by dependabot.

Before merging, check for compatibility.

Update to Helm3

The Helm + Tiller combination dependencies should be updated to use newer versions of Helm.

Uniform Standards Request: Experimental Repository

Hello!

We believe this repository is Experimental and therefore needs the following files updated:

• The Experimental badge
• The Experimental Statement in the README.md
• Getting Started Tutorial
• README.md
• LICENSE
• CI/CD
• OWNERS.md
• Developer Certificate of Origin
• At least one maintainer

If you feel the repository should be maintained or end of life or that you'll need assistance to create these files, please let us know by filing an issue with https://github.com/packethost/standards.

Equinix Metal maintains a number of public repositories that help customers to run various workloads on Equinix Metal. These repositories are in various states of completeness and quality, and being public, developers often find them and start using them. This creates problems:

• Developers using low-quality repositories may infer that Equinix Metal generally provides a low quality experience.
• Many of our repositories are put online with no formal communication with, or training for, customer success. This leads to a below average support experience when things do go wrong.
• We spend a huge amount of time supporting users through various channels when with better upfront planning, documentation and testing much of this support work could be eliminated.

To that end, we propose three tiers of repositories: Private, Experimental, and Maintained.

As a resource and example of a maintained repository, we've created https://github.com/packethost/standards. This is also where you can file any requests for assistance or modification of scope.

The Goal

Our repositories should be the example from which adjacent, competing, projects look for inspiration.

Each repository should not look entirely different from other repositories in the ecosystem, having a different layout, a different testing model, or a different logging model, for example, without reason or recommendation from the subject matter experts from the community.

We should share our improvements with each ecosystem while seeking and respecting the feedback of these communities.

Whether or not strict guidelines have been provided for the project type, our repositories should ensure that the same components are offered across the board. How these components are provided may vary, based on the conventions of the project type. GitHub provides general guidance on this which they have integrated into their user experience.

"k3sup app install" is now "arkade install"

FYI, you may want to rename some of your commands where you use k3sup app install, which has now become arkade install

I believe there was one or two usages of k3sup app install in the repo.

More at: https://get-arkade.dev/

Thanks

Alex