moving to v1.0 beta release

[andyxning]

Before we make node-feature-discovery to a beta release, we need to do things below finished.
Note: This check list is not thorough full. It may change in the future.

• move import path from github.com/kubernetes-incubator to k8s.io.
• make an agreement on the label schema about node-feature-discovery. change label namespace #71
• adjust node-feature-discovery to meet the requirements to be a Kubernetes repo described in kubernetes-template-project.
• make an agreement on the release schedule (v1.0 beta and GA) for node-feature-discovery.
• update client-go to newest stable version.
• replace glide with godep.
• decide which registry (quay.io or gcr.io) to use.
• change node-feature-discovery image namespace from kubernetes-incubator to kubernetes.
  /cc @ConnorDoyle @balajismaniam

[marquiz]

The host organization of NFD was briefly discussed in the SIG-node meeting 2018/07/10. The opinion was more inclined into moving NFD under Kubernetes SIGs organization instead of Kubernetes core.

I think this issue could be closed, for now. A new issue tracking the progress on moving under kubernetes-sigs should be created.

What do you think @balajismaniam @andyxning @ConnorDoyle?

[andyxning]

@marquiz Any docs or record video about the discussion.

[marquiz]

Hmm, it seems that the last recording from SIG-node meeting is from April, so I'm afraid the answer is no. But, this was still a preliminary discussion. I think there needs to more evidence on the health of the nfd project and its benefits before the move under sig-node will be considered

[andyxning]

I think there needs to more evidence on the health of the nfd project and its benefits before the move under sig-node will be considered

Agreed. We need first make nfd more common, imo, the support for the hardware detect is somewhat too detail, and collect more user cases. As for the detailed collect, it do not mean that it is not necessary, but maybe some common useful ones are more demanded. :)

[marquiz]

As for the detailed collect, it do not mean that it is not necessary, but maybe some common useful ones are more demanded.

Hmm, I don't know if I quite understand what you mean here. Do you have some specific features in mind?

[marquiz]

NFD was migrated to kubernetes-sigs organization. Remaining work items related to the change are tracked in #175.

Closing this issue as I don't think it is relevant, anymore. The label names(pace) are going to be changed to more generic, without any alpha/beta/ga status encoded in the name.